Use Ox as serializer

[najamelan]

Ox is an object serializer which is faster than Marshal. I wonder if you'd be interested in a pull request that uses Ox in parallel?

Question is whether it's ok to add a dependency which requires compilation or rather use Ox if available and Marshal otherwise?

https://github.com/ohler55/ox
http://www.ohler.com/dev/ruby_object_xml_serialization/ruby_object_xml_serialization.html

[grosser]

How about allowing the serializer to be configured ? :)

…

On Wed, Jan 25, 2017 at 5:19 AM, Naja Melan ***@***.***> wrote: Ox is an object serializer which is faster than Marshal. I wonder if you'd be interested in a pull request that uses Ox in parallel? Question is whether it's ok to add a dependency which requires compilation or rather use Ox if available and Marshal otherwise? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#194>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAsZ7zjA9REn5gqzMaC7DFGbv0GcTlNks5rV0v3gaJpZM4LteaO> .

[ms-ati]

+1 for allowing the serializer to be configured, and giving an example in the README of using Ox!

[grosser]

how about a PR ? :)

…

On Fri, Feb 10, 2017 at 7:41 AM, Marc Siegel ***@***.***> wrote: +1 for allowing the serializer to be configured, and giving an example in the README of using Ox! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#194 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAsZ7iTBOQlI0jykL8SIUPWIvh6uUmtks5rbIUQgaJpZM4LteaO> .

[najamelan]

I'm sorry I didn't get back to you about this. I was looking into dealing with performance issues by parallelizing, and when considering Parallel this came to mind. But then I realized I had quite big data structures that would need to be available to my working processes and that seemed a hassle, passing through redis which needs two more serialize operations to get data around. Then I though, damn, I would really be better of doing real multithreading, so I looked into jruby, which didn't really run refinements the way I need them to, rubinius didn't work either for some reason I already forgot, and so now I'm extending my app with a lib in rust that I'm working around the clock to implement. Faster work in the first place and I can multithread it on top of that without serializing. That's pretty much better than anything I can do with ruby directly.

So, since I'm working against a deadline, I won't be able to work on this proposal this week. In itself it looks like it's trivial to implement, so I wouldn't mind but I can't make promises right now. I will try to find some time next week to look into it.