New server status (in General)
February 15 2007 12:20 PM EST
Shipped the new server off to the colo facility today. It will arrive next Wednesday; I'll be at PyCon from Wednesday until Sunday, so Saturday March 3 is a likely time to take the new one live.
The new machine has 8GB of ram and 6 15k rpm SCSI disks, so I'm looking forward to it. :)
February 15 2007 12:21 PM EST
Great Jonathan :)
February 15 2007 12:23 PM EST
You're a genius! thanks!
February 15 2007 12:56 PM EST
And the co-locating means better bandwidth reliability? Or isn't that an issue any more?
Thanks DAWG! Oh wait..
Great work Jon :)
hahah.. I thought colo was short for Colorado =)
February 15 2007 1:12 PM EST
"the co-locating means better bandwidth reliability?"
that's what I'm hoping, we've been having downtime around once a month with csolutions lately which is pretty ridiculous
February 15 2007 1:37 PM EST
Better all the way 'round! Thank you, fearless leader!
things will be shine y in the future
February 15 2007 1:57 PM EST
8GB ought to be enough for anybody.
heh eight gigs should be, but I bet an oracle install with some weight could eat that much ram up in seconds...
it's those 15k rpm disks I'm drooling over...
February 15 2007 2:17 PM EST
Its would be great if you could give us more information on the sever.CPU chipset Ram type.....
February 15 2007 2:23 PM EST
What was the final bill for that beast?
Statistic wise, How much better is the new server compared to the old?
"8GB ought to be enough for anybody."
640K will be plenty of RAM for user space programs.......
Xiaz on Hiatus
February 15 2007 7:42 PM EST
Maybe, we can have graphics now? :D
February 15 2007 8:19 PM EST
meh...who wants graphics?
February 15 2007 8:35 PM EST
Maybe we can have a few hundred more players? I'm tired of fighting people half of my score.
February 15 2007 8:53 PM EST
Woo! NPCs! ;)
This thread is closed to new posts.
However, you are welcome to reference it
from a new thread; link this with the html
<a href="/bboard/q-and-a-fetch-msg.tcl?msg_id=0021wQ">New server status</a>