05-21-2010, 06:22 AM
What I meant to say by 'up to date hardware' is a Docsis 3.0 cable modem.
A lot of people don't have that and don't realize it's needed to fix a lot of issues, even if their previous speeds are doing ok. Nothing to do with the computer.
Anyway, like you say, like I said before, you are correct, the internet speed and computer are really two separate things. I was just pointing out that if you can sustain good speeds, then it's a non-issue. I'm sure some people have problems with it. Maybe they shouldn't be running servers. But does that have anything to do with running the client on the same machine? So I don't see the point of debating speed.
I don't know if it's changed, but last time I had a server set up cs source coudln't even take advantage of multiple cores. it was stuck on one. (not sure about srcds, or either now that it's two years later) The proposed idea in this thread is 'don't run a server and client on the same pc - why? - it's bad'. The reason my stance is so strong against it is because I've not seen any good evidence supporting that reason.
If the supposition is changed to 'don't run a client and a server on the same pc with a crappy connection' then ok, I get that.
But if that is the case, then why would running the client on the server matter? The client is 0 tick to the server that way. Then maybe the case should be 'Don't run a game server with a crappy connection'? That makes even more sense.
However, the side supporting the idea of the op continues to drift into the issue of how a home connection isn't ideal for a server, in some effort to justify why you shouldn't run the two together.
So let's just take the connection issue out of it. I go up to the itd department and gaming club at the local college and ask to leave my box up there to run a server on. Their fiber connection is a non-issue. Now can I boot up the client on the server? What becomes the qualification for good performance at this point? More simply, what are the MINIMUM requirements to run the serve at XX tickrate, coupled with the minimum requirements for running the client well.
--------------------------
An example answer, (likely not accurate and JUST an example), would go something like:
A 66tick server needs a single core from a 2.0ghz core 2 duo or Pentium D arch with 2gb of ram minimum to function flawlessly.
The client needs a single core from a minimum of a 2.4ghz core 2 duo along with 2gb of ram and a geforce 9600.
Thus a good starting point would be an E8000 series processor and 4gb's of ram to run both effectively. Don't forget to lock your cores.
(this is just and idea of a reccomendation and may not exclude this setup from performing similarly on lower hardware or maybe using a linux distro.)
[edit oh wow this got long quick. lol. sorry.]
A lot of people don't have that and don't realize it's needed to fix a lot of issues, even if their previous speeds are doing ok. Nothing to do with the computer.
Anyway, like you say, like I said before, you are correct, the internet speed and computer are really two separate things. I was just pointing out that if you can sustain good speeds, then it's a non-issue. I'm sure some people have problems with it. Maybe they shouldn't be running servers. But does that have anything to do with running the client on the same machine? So I don't see the point of debating speed.
I don't know if it's changed, but last time I had a server set up cs source coudln't even take advantage of multiple cores. it was stuck on one. (not sure about srcds, or either now that it's two years later) The proposed idea in this thread is 'don't run a server and client on the same pc - why? - it's bad'. The reason my stance is so strong against it is because I've not seen any good evidence supporting that reason.
If the supposition is changed to 'don't run a client and a server on the same pc with a crappy connection' then ok, I get that.
But if that is the case, then why would running the client on the server matter? The client is 0 tick to the server that way. Then maybe the case should be 'Don't run a game server with a crappy connection'? That makes even more sense.
However, the side supporting the idea of the op continues to drift into the issue of how a home connection isn't ideal for a server, in some effort to justify why you shouldn't run the two together.
So let's just take the connection issue out of it. I go up to the itd department and gaming club at the local college and ask to leave my box up there to run a server on. Their fiber connection is a non-issue. Now can I boot up the client on the server? What becomes the qualification for good performance at this point? More simply, what are the MINIMUM requirements to run the serve at XX tickrate, coupled with the minimum requirements for running the client well.
--------------------------
An example answer, (likely not accurate and JUST an example), would go something like:
A 66tick server needs a single core from a 2.0ghz core 2 duo or Pentium D arch with 2gb of ram minimum to function flawlessly.
The client needs a single core from a minimum of a 2.4ghz core 2 duo along with 2gb of ram and a geforce 9600.
Thus a good starting point would be an E8000 series processor and 4gb's of ram to run both effectively. Don't forget to lock your cores.
(this is just and idea of a reccomendation and may not exclude this setup from performing similarly on lower hardware or maybe using a linux distro.)
[edit oh wow this got long quick. lol. sorry.]