.net - Load testing strategies for network server applications -
i building windows service listens connections on tcp and, once connection established, sends steady stream of data. simple... once initial request made, communication one-way (on application layer, of course).
what way test significant load, 3,000 simultaneous connections? there standard tools kind of thing, or should write own?
i have feeling have written own protocol, think you're stuck implementing own load testing client.
writing load testing client isn't hard. thing advise though think whether you're going test on connection 1 physical machine or multiple. i'm not saying should test 3,000 physical machines, 10 or 20 machines idea. otherwise have chance client machine being bottleneck.
also, test server, have have load test implementation. if see processor usage of load tester staying @ 100%, you're not testing server; you're testing client.
Comments
Post a Comment