Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am currently working on a test use case where I need to test performance (benchmark) between a server/computer and smart-devices (tablet, smartphones etc.). The benchmark I want to do is based on LAN performance with normal TCP/IP sockets vs. WebSockets.

I am not quite sure where to begin, and I need to find a solution that fits both Android and iOS.

EDIT: iperf seems to be the way to go with testing TCP and UDP performance, since there is applications for all platforms..

share|improve this question

Set up a mini SpeedTest server and you can do latency and transfer speed tests.

share|improve this answer
Great suggestion! But unfortunately i understand SpeedTest is based on SWF which is incompatible with iOS. – JavaCake Apr 10 '13 at 19:22
@JavaCake Mobile Apps :) – Kruug Apr 10 '13 at 19:24
i might have been a little unclear. I need to make this test on LAN, and not internet, the SpeedTest mini server was a potential solution for this task. – JavaCake Apr 10 '13 at 19:34

You could use iperf. There are Apps for Android and iOS

share|improve this answer
I cannot really see if the Android app supports iperf v3 or not, else i need to stick to v2. – JavaCake Apr 10 '13 at 20:05
I assume its v2.0.5, 5$ well spend :-) – JavaCake Apr 10 '13 at 20:08
I can't tell which versions of iperf are supported sorry, I don't use it myself. 5$? In my play store it is free! – Simon Apr 10 '13 at 20:14
For iOS its unfortunately pricey, but the app seems to work. Do you by any chance have an suggestion for testing WebSockets? – JavaCake Apr 19 '13 at 9:28

An old utility for testing TCP/UDP throughput is called ttcp. It was written by the same fellow who wrote ping. One host sets itself up as a receiver with ttcp -rs and the other host transmits to the receiver (default port 5001), with ttcp -ts <receiver host>. It's highly configurable, provides stats, and has been ported to multiple platforms.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.