Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

1M messages passes in 34 microseconds would be ~0.1 CPU clocks per message pass. Maybe an optimizer is stepping in and short-circuiting?


heh, not only that, but my fingers accidentally made my test massively concurrent! Such are the perils of erlang. When I defeat the optimizer and also force message passing to be serialized both inside and outside a trial, I get an average of 525000 microseconds, which is more in line with the other results.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: