Comments on: Of MySQL/Ruby, EventMachine, and the need for non-blocking APIs http://blog.playlouder.com/2008/05/12/of-mysqlruby-eventmachine-and-the-need-for-non-blocking-apis/ rewriting the rules of music online Wed, 30 Sep 2009 17:06:37 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Markus Jais on software development » 9 websites about Ruby/EventMachine http://blog.playlouder.com/2008/05/12/of-mysqlruby-eventmachine-and-the-need-for-non-blocking-apis/comment-page-1/#comment-5013 Markus Jais on software development » 9 websites about Ruby/EventMachine Fri, 09 Jan 2009 21:37:16 +0000 http://blog.playlouder.com/?p=90#comment-5013 [...] Of MySQL/Ruby, EventMachine, and the need for non-blocking APIs. Great post about non-blocking APIs and why they are important. [...] [...] Of MySQL/Ruby, EventMachine, and the need for non-blocking APIs. Great post about non-blocking APIs and why they are important. [...]

]]> By: matthew http://blog.playlouder.com/2008/05/12/of-mysqlruby-eventmachine-and-the-need-for-non-blocking-apis/comment-page-1/#comment-5005 matthew Wed, 03 Sep 2008 11:14:27 +0000 http://blog.playlouder.com/?p=90#comment-5005 [quote comment=""] Anyway you can also lookup mysqlplus for another ruby mysql non-blocking drivers, hopefully with good success :) [/quote] Aha, yes spotted this the other day. This pretty much solves the problem, great work! (For anyone following: http://github.com/oldmoe/mysqlplus/tree/master )

Anyway you can also lookup mysqlplus for another ruby mysql non-blocking drivers, hopefully with good success :)

Aha, yes spotted this the other day. This pretty much solves the problem, great work!

(For anyone following: http://github.com/oldmoe/mysqlplus/tree/master )

]]> By: rogerdpack http://blog.playlouder.com/2008/05/12/of-mysqlruby-eventmachine-and-the-need-for-non-blocking-apis/comment-page-1/#comment-5003 rogerdpack Tue, 02 Sep 2008 19:16:09 +0000 http://blog.playlouder.com/?p=90#comment-5003 Fascinating. I had no idea the ruby mysql drivers were non-blocking. Nice! Anyway you can also lookup mysqlplus for another ruby mysql non-blocking drivers, hopefully with good success :) -=R Fascinating. I had no idea the ruby mysql drivers were non-blocking. Nice!

Anyway you can also lookup mysqlplus for another ruby mysql non-blocking drivers, hopefully with good success :)

-=R

]]> By: Sérgio Gomes http://blog.playlouder.com/2008/05/12/of-mysqlruby-eventmachine-and-the-need-for-non-blocking-apis/comment-page-1/#comment-3814 Sérgio Gomes Thu, 22 May 2008 12:03:50 +0000 http://blog.playlouder.com/?p=90#comment-3814 Hi matthew, You're absolutely right! I just gave it a try and it nicely ran everything in parallel :) My queries are simple (I'm not even using Rails), so this is definitely the best option. Thanks! Sérgio Hi matthew,

You’re absolutely right! I just gave it a try and it nicely ran everything in parallel :)

My queries are simple (I’m not even using Rails), so this is definitely the best option.

Thanks!
Sérgio

]]> By: matthew http://blog.playlouder.com/2008/05/12/of-mysqlruby-eventmachine-and-the-need-for-non-blocking-apis/comment-page-1/#comment-3813 matthew Thu, 22 May 2008 11:57:13 +0000 http://blog.playlouder.com/?p=90#comment-3813 Sergio, If scalability/concurrency matters more than speed you could give the native Ruby MySQL API a try. I believe this is non-blocking on Ruby threads as it uses the native ruby libraries for its IO. To do this you have to do: require 'active_record/vendor/mysql' require 'activerecord' to stop activerecord loading the C-extension-based mysql gem. This isn't ideal though, the native ruby implementation is a fair bit slower and doesn't seem to be recommended for production use. It's worked ok for us although haven't really tested it under high load yet. Sergio,

If scalability/concurrency matters more than speed you could give the native Ruby MySQL API a try. I believe this is non-blocking on Ruby threads as it uses the native ruby libraries for its IO.

To do this you have to do:

require ‘active_record/vendor/mysql’
require ‘activerecord’

to stop activerecord loading the C-extension-based mysql gem.

This isn’t ideal though, the native ruby implementation is a fair bit slower and doesn’t seem to be recommended for production use. It’s worked ok for us although haven’t really tested it under high load yet.

]]> By: Sérgio Gomes http://blog.playlouder.com/2008/05/12/of-mysqlruby-eventmachine-and-the-need-for-non-blocking-apis/comment-page-1/#comment-3812 Sérgio Gomes Thu, 22 May 2008 11:47:58 +0000 http://blog.playlouder.com/?p=90#comment-3812 I'm running into exactly that issue; I need to connect to several databases and query them simultaneously, and I guess the only way I could do that right now would be to have a separate *process* for each one and use IPC. Not pretty or simple... If you do come across any solution, even if just experimental, please let me know; otherwise I'll have to implement the process option or code a python script just for that. Cheers, Sérgio I’m running into exactly that issue; I need to connect to several databases and query them simultaneously, and I guess the only way I could do that right now would be to have a separate *process* for each one and use IPC. Not pretty or simple…

If you do come across any solution, even if just experimental, please let me know; otherwise I’ll have to implement the process option or code a python script just for that.

Cheers,
Sérgio

]]>