[erlang-questions] Erlang to Python

Michael Turner michael.eugene.turner@REDACTED
Sun Aug 7 08:51:42 CEST 2011

I wrote: "the performance problem of serializing to JSON"

Oops. JSON *de*-coding seems to be issue.

But wasn't CouchDB the beneficiary of some NIF JSON parser 10x faster
than mochijson?

-michael turner

On Sun, Aug 7, 2011 at 2:12 AM, Michael Turner
<michael.eugene.turner@REDACTED> wrote:
> Part of their problem might have been architectural:
> "In Erlang, the right way to do this is to spawn off a separate set of
> actors to manage each data structure and message pass with them to
> save and retrieve data. Our code was not set up this way at all, and
> it was clearly crippled by being haphazardly implemented in a
> functional style."
> I'd suggest a friendly request to mixpanel to open-source their
> now-disused Erlang code - it might be instructive both about how their
> code could have been better and about how Erlang might need to
> improve.
> I wonder ... what seems to be the performance problem of serializing
> to JSON might actually be a latency problem - if the managing process
> for some data wakes up every now and then, with medium-to-low
> priority, and re-serializes if necessary, to be ready to respond to
> such requests, it might make all the difference in the world. OK, it
> might make *some* of the difference in the world.
> -michael turner
> On Sun, Aug 7, 2011 at 1:55 AM, Robert Virding
> <robert.virding@REDACTED> wrote:
>> Saw this on reddit. Any comments?
>> http://code.mixpanel.com/2011/08/05/how-and-why-we-switched-from-erlang-to-python/
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions

More information about the erlang-questions mailing list