Webhostingtalk.com loads so darn fast. I wonder what kind of hosting or dedicated service is it using and what kind of system is it running its stuff on.

Last time I know the primary server, www.webhostingtalk.com, is hosted at voxel.net using dual P3/750Mhz with 512MB memory and 2x9GB SCSI drives (I think it's 7200rpm SCSIs, cmiiw).

Now ... I am more interested to know about www2.webhostingtalk.com, the secondary server ... It's hosted by datacolo (yea, Carlos!) and it does not load fast (quite a bit slower than the primary server). The reason (I think) is not because datacolo is slower, but rather, I believe, the secondary server (www2) is doing remote mysql db off the primary server (www), hence the slowness ... Also, I wonder what the specs on the secondary server ...

cheers,
:beer:

Wow, Voxel.net's virtual hosting costs so much. Is that why its so fast? Cause its like 145 dollars for 10 gigs/permonth
Os Webhostingtalk.com using virtual hosting?

Originally posted by dektong
Last time I know the primary server, [url]The reason (I think) is not because datacolo is slower, but rather, I believe, the secondary server (www2) is doing remote mysql db off the primary server (www), hence the slowness ... Also, I wonder what the specs on the secondary server ...

correct, the mirror has to connect to the remote DB on the primary server, while this makes it considerably slower for people wih fast connections, it is faster for people with slower connections to Voxel (expecially overseas)

The server is a Simple PIII 866 with 512MB of ram and 40GB HD

mysql has this replication feature available where you can basically setup master and slave db on two different servers and synchronize the two dbs simultaneously ... I think it's a better option than doing remote mysql for at least two reasons: First, you will transfer the same amount of bandwith between the two servers either using replication or remote connection methods. Second, you will have two totally independent/redundant sites such that if the primary server goes down, the secondary can kick in serving pages (can't do this with remote mysql).

I still need to learn how to use this replication feature on mysql. But I think WHT should definitely look into this.

cheers,
:beer:

Originally posted by CRego3D
while this makes it considerably slower for people wih fast connections, it is faster for people with slower connections to Voxel (expecially overseas)


May I know why? I think it will even make it slower since the secondary server (www2) will still need to connect to voxel to do remote mysql off the primary server anyway. I don't see how this can improve anything .... I believe mysql replication is the way to go otherwise most people (including me the first time I tried www2) will just think that the connectivity to data colo must be not that great, at least from my location.

cheers,
:beer:

If any one knows where i can find out an easy way to setup mysql replication i would love to know.. :)

Please not a book on it some thing simple the basics.. hehe

I don't think there is an easy way to set this up, but I was given this link (http://www.mysql.com/doc/manual.php?search_query=replication&depth=0) to start. I am learning it now ...

cheers,
:beer:

Originally posted by dektong


May I know why? I think it will even make it slower since the secondary server (www2) will still need to connect to voxel to do remote mysql off the primary server anyway. I don't see how this can improve anything .... I believe mysql replication is the way to go otherwise most people (including me the first time I tried www2) will just think that the connectivity to data colo must be not that great, at least from my location.

cheers,
:beer:

Not really, some users were experiencing several problems in connecting to Voxel's netwokr, some where even unable to check WHT at all, since the www2 server is the one who is taping into the www, and not the user, they are able to connect faster.

for those people is the reason the www2 was created :), unfortunately the system is not setup as a "backup" (in case the main one goes down" .. something "mysql replication" would do .. we shall see in the future :)

Originally posted by CRego3D
Not really, some users were experiencing several problems in connecting to Voxel's netwokr, some where even unable to check WHT at all, since the www2 server is the one who is taping into the www, and not the user, they are able to connect faster.


I still don't get it (probably it's time for me to go to bed again), but if somebody is going to get problem connecting to voxel, how then he will access www2 without problem where www2 needs to connect into www (at voxel) for its remote mysql operations?

cheers,
:beer:

Originally posted by dektong


I still don't get it (probably it's time for me to go to bed again), but if somebody is going to get problem connecting to voxel, how then he will access www2 without problem where www2 needs to connect into www (at voxel) for its remote mysql operations?

cheers,
:beer:

hehe, it is time for bed :D

Problem .. User 1 has a 600ms lag to connect to Abovenet, but only a 100ms lag to connect to www2

www2 has a lag of 40ms to connect to www

User 1 only has a 140ms lag by using www2 instead of 600ms lag if he connects to www

get it now ? :)

once again, that's why this was created, you must remeber a few months back there where a few users (expecially overseas) having major issues connection to www ..

ah OK ... Sorry for the silly questions then, I did need time to go to bed :D

Another thing ... I see that www and www2 are not actually load balancing solutions ... I don't think it's that hard to set this up, well at least using Round Robin schemes ... Perharps one day Matt will look into setting load balanced WHT, with two independent servers?

cheers,
:beer:

correct, unfortunately it is not a load balancing solution .. hopefully in the future Matt will set it up like that :)