Sythe.org speedups

[Eru]

http://puu.sh/1w065

Got the same problem as Laptop65 has.

 

http://puu.sh/1w065

Got the same problem as Laptop65 has.

Should resolve itself when your DNS updates.

 

[Laptop65]

That is pretty bad. What browser are you running. Also when you ping sythe.org what IP shows up?

Thanks

I'm using Firefox, latest beta version.

If I ping the site I get -

Took me 6 refreshes to get to here and load the pages fully.

 

[Syed]

Mind indulging us on what you updated exactly, if new hardware, mind telling us the setup? As in what hardware you're using.

 

Mind indulging us on what you updated exactly, if new hardware, mind telling us the setup? As in what hardware you're using.

I don't want to give too many specifics for security reasons. Basically we're completely on ssd raid disks now, and I've spent a lot of time changing the backend architecture of the site so that it can be distributed across many smaller nodes. This allows me to add or remove nodes to suit load. On the front end we're using cloudflare for the moment, which seems to be working quite well.

When you ping sythe.org, if you still get an IP starting with 74, or 65, then your DNS hasn't updated and you're still on the old front-end. I think the half-page-loads was an artefact of lighttpd's mod_proxy (which we previously used for our front-end, before cloudflare.) Anyway I've changed that old front end server to use nginx for the moment. So hopefully anyone who still has the half-page-load problem will still have a better browsing experience until their DNS updates.

 

[I Peter I]

Since the updates were implemented yesterday I haven't received any ERR_NO_RESPONSE errors. Those were the only ones I was getting in the first place and they seem to have been resolved. Cheers.

 

I don't want to give too many specifics for security reasons. Basically we're completely on ssd raid disks now, and I've spent a lot of time changing the backend architecture of the site so that it can be distributed across many smaller nodes. This allows me to add or remove nodes to suit load. On the front end we're using cloudflare for the moment, which seems to be working quite well.

When you ping sythe.org, if you still get an IP starting with 74, or 65, then your DNS hasn't updated and you're still on the old front-end. I think the half-page-loads was an artefact of lighttpd's mod_proxy (which we previously used for our front-end, before cloudflare.) Anyway I've changed that old front end server to use nginx for the moment. So hopefully anyone who still has the half-page-load problem will still have a better browsing experience until their DNS updates.

I've used 64.92... for a long time will I get any better speed changing to cloudflare front-end?

 

I've used 64.92... for a long time will I get any better speed changing to cloudflare front-end?

Yeah much better speeds. 2-3 sec page loads instead of 4-7.

 

Yeah much better speeds. 2-3 sec page loads instead of 4-7.

Damn right. Much faster now.

Great update Richard

 

[Laptop65]

How do you you update your DNS? Or is it an ISP thing? Seems I'm still connecting to the 74. server(s).

 

How do you you update your DNS? Or is it an ISP thing? Seems I'm still connecting to the 74. server(s).

I'm sure you must be using your ISP DNS servers. As soon as their cache expires you'll get new IPs

You can try using Google's DNS servers. Or Comodo's or OpenDNS. ^_^ ^_^

 

[iJava]

What RAID are you using? Seems to be much faster, also are you on the free CloudFlare plan?

 

What RAID are you using? Seems to be much faster, also are you on the free CloudFlare plan?

We're on RAID 1+0, but the important bit is that all the disks (except a few holding backups of the core db) are SSD, which means they are blazing fast. Previously our main bottleneck was IO speed.

 

[iJava]

We're on RAID 1+0, but the important bit is that all the disks (except a few holding backups of the core db) are SSD, which means they are blazing fast. Previously our main bottleneck was IO speed.

Figured you'd do 1+0 as it's the most cost effective. Have you thought of hosting the site on three different servers, 1 for Database, one for images etc and the other for the forums?

 

[blazee]

Haven't had any errors what-so-ever the past few hours.

Running Google Chrome.

 

[Laptop65]

Well if I ping it again I seem to get packet loss when I ping through cmd.

However a new IP shows up and the site indeed is a lot faster than before. I've yet to experience the half page loading error as of yet too. Nice one Richard!

 

I'm also getting around a 50% packet loss when I ping the IP 108.162.192.167.

 

[Noam]

Figured you'd do 1+0 as it's the most cost effective. Have you thought of hosting the site on three different servers, 1 for Database, one for images etc and the other for the forums?

Pretty sure that's already the case
I know there's an image(s?).sythe.org server and the three front end www ww2a and ww3 and I expect something along the lines of a backend one is bound to exist

 

Pretty sure that's already the case
I know there's an image(s?).sythe.org server and the three front end www ww2a and ww3 and I expect something along the lines of a backend one is bound to exist

Yes, at our peak we had 6 servers. We are going back down to 4 now the server move is complete. I will add more as needed to keep the load down.

 

[Laptop65]

Is it me or has Cloudflare changed the entire site's URLs? For example if you hover over a thread it displays the link different now with words and stuff in the link.

New - http://www.sythe.org/request-pardon/1496609-punkerpunk13-high-pardon.html

Old - http://www.sythe.org/showthread.php?t=1496609

Is this part of making the site faster? Or did CloudFlare do it automatically?