Jump to content
  • Advertisement
Sign in to follow this  

Stress Testing

This topic is 2340 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts


I've written a dissertation project which includes a client and game server application. To stress test the application, I've built a special client which hits the server with a huge number of connections, and run the test twice with two server configurations.

If I presented you with the total connections completed, average time to complete those connections and average CPU/Memory usage of the server - and concluded that one configuration was better - what information about the tests would you want to know in order to believe me?

It might be difficult to say without knowing specifics about the application, but perhaps there is something general?

- Server Hardware?
- Network Link Speed?
- Number of server threads used?
- Time duration of the tests?

Any suggestions would be hugely appreciated.

Many thanks :)

Share this post

Link to post
Share on other sites
Just accepting connections should be virtually free if you used a good implementation strategy; you should be able to handle a few hundred thousand sockets before noticing any significant degradation of service.

Accepting connections and processing requests from those connections is much more interesting, IMHO.

Share this post

Link to post
Share on other sites
Sign in to follow this  

  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!