Building server hows this hardware?

[Derision]

Originally Posted by paaco

It does not take advantage of quad core.

I would have thought it would, since each zone.exe is a separate process, so if you had four or more zones with players in, the main thread of up to four zones should be dispatched on each core simultaneously, providing they weren't waiting for DB access. I run my private server on on an old single core Hyperthreading CPU (ShuttleX) , so I've never actually looked into how it utilises multi-cores.

[Rhodan]

Looking at my XP Pro box running 60+ zones the processors both see activity when I do things with the game so I'm thinking that the OS is load balancing across the CPUs.

I don't think that's the same as the program taking advantage of the CPUs. And I'm (wildy) guessing that if four zones were heavily used you could end up with all the load on one processor.

[paaco]

Hmm yeah thinking about it that way the OS probably does load balance across all 4 cores. I run mine on a Phenom 9850 Quad core, I have never payed attention to that though.

When I answered the question I was only thinking about the eq client not being optimized for dual/quad core. My mistake, I apologize for not thinking about it first ;p

[trevius]

I recently upgraded my server to a Dual Core CPU and it seems to load balance pretty well. I imagine that it just loads zones and splits them between the processors.

The deciding factor for most servers is upload bandwidth. With 1MB up, you can get about 80-100ish players on without too many performance issues. For more than that, you would need more upload bandwidth.

[Yeormom]

All of your zones will each support the ability to have their infinity set to a different core, but world.exe will obviously only run on one. Your only problem is going to be bandwidth, as it looks like your talking about residential cable for Internet. It might also be nice to have some additional storage for backups.

[Rhodan]

Well I took a shot at leading every .map statically (283?) on a 4 gig machine. Got as far as TakC (253 I think) before having problems. TakD and on would end up restarting over and over again. At the end I had almost 6 gigs of paged data and just shy of 400 megs of ram free.

Each loaded zone ran as a separate process and there were multiple threads created for each zone (over 1400 threads were running though some were unrelated to eqemu of course).

I'm going to cut out a bunch of maps (earlier in the alphabetical listing) just to make sure it was memory restraints that caused the failure to load the maps.

[hayward6]

Just curious, but why are you trying to open up all the zones? you can set it up for say 100 consecutive random zones and as people move between them the zones will open and close to free up resources. Since you can now set your zones to save state when they shut down, you don't really lose anything... just some thoughts.

Also, if you're looking to go big with this server like it looks you are... you're going to be much better off running it on a Linux box.