[erlang-questions] tcp server benchmark

[Jon Watte]

Benchmarks are only useful to judge the performance of the exact thing the
benchmark is measuring.

If you don't know what it is, exactly, that you want to measure, then any
numbers you could come up with would possibly be totally meaningless,
because numbers only have meaning when they influence decisions, and
decisions are made based on specific requirements.

So, start there: What decision are you going to make based on numbers?
Then, you can figure out: What numbers do you actually need to make that
decision?
Then, you can figure out how to actually get THOSE numbers, and not some
other numbers...



Sincerely,

Jon Watte


--
"I pledge allegiance to the flag of the United States of America, and to
the republic for which it stands, one nation indivisible, with liberty and
justice for all."
~ Adopted by U.S. Congress, June 22, 1942



On Wed, Apr 18, 2012 at 1:19 AM, eigenfunction <emeka_1978@REDACTED> wrote:

> There has been a lot of mails recently about benchmarking stuff. Now i
> am faced with the task of benchmarking a tcp server so i am curious.
> Is there any simple way out there to benchmark an erlang tcp server
> without having to hack some linux script? I was expecting it to be a
> simple task but after i started writing the client, i had to stop a
> think first about what exactly i want to measure. single client
> sending 1000 messages vs 1000 clients sending 1 messages vs multicore
> vs single core and it is getting more and more complicated as i think
> about it. How do you guys go about it?
> Thanks.
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20120419/cd243ace/attachment.htm>