Re:Msgpack can't differentiate between raw binary data and t...
by duaneb on Saturday February 23, 2013 @07:47AM
(#5269511)
> I write web software in Ruby that runs on embedded devices.
Ok I gotta ask.... Why on earth would you do that? It seems like an exercise in masochism. I wasn't even aware that ruby would compile on embedded arches.
Re:Msgpack can't differentiate between raw binary data and t...
by nitrogen on Saturday February 23, 2013 @07:51AM
(#5269518)
High-end embedded Linux (1.2GHz ARM CPUs). It saved development time, but I am considering rewriting everything in C. This is an example of what it's for (self-promoting link in 3, 2, 1...): http://www.nitrogenlogic.com/
Re:Msgpack can't differentiate between raw binary data and t...
by duaneb on Saturday February 23, 2013 @11:19AM
(#5270145)
Ahh, you mean literally embedded (perfectly legitimate use of the word). I associate it with DSPs and extremely low power chips where something like ruby is an absurdity. ARM is a great target for it, though.
Re:Msgpack can't differentiate between raw binary data and t...
by badgar on Saturday February 23, 2013 @03:20AM
(#5268991)
Have you tried using thrift or protocol buffers, which aren't self-describing (introducing enormous overhead for <1MB messages.
Re:Msgpack can't differentiate between raw binary data and t...
by nitrogen on Saturday February 23, 2013 @03:40AM
(#5269028)
I haven't. I'd expect them to be faster, but my biggest issue is CPU time rather than throughput. At any rate, my current solution is no longer a bottleneck on performance, but if it becomes one, I'll definitely be looking into other binary serialization formats.
Edit: here are my results, which lack the numbers for msgpack except a mention at the end (I hate linking to Posterous, but I haven't moved my blog yet): http://nitrogen.posterous.com/164964342