Comments on: MRI Ruby + MySQL + Threads == Stop the world… JRuby doesn’t

By: roger

roger — Wed, 27 Aug 2008 15:04:00 +0000

Appears that MRI works with 1.8.6 if you do the following:
compile the oldmoe drivers, require them instead of the gem,

replace line 49:

res = conn.query(sql_statement)

with

conn.send_query(sql_statement)
socket = IO.new(conn.socket)
result = select([socket], nil, nil, nil)
res = conn.get_result

=> Multi-threaded: 1.0046272277832s

By: Justin Marney

Justin Marney — Wed, 27 Aug 2008 15:04:00 +0000

I was curious on how the postgres benchmarks actually looked/worked so I added the ability to generate them to the test.

http://pastie.org/261782

jmarney:Desktop $ postgres=true ruby db_locking_test.rb

Loading MRI Postgres
Serial: Testing 4 iterations
thread: # executing: select pg_sleep(1)
thread: # executing: select pg_sleep(1)
thread: # executing: select pg_sleep(1)
thread: # executing: select pg_sleep(1)
Serial: 4.02708697319031s
Multi-threaded: Testing 4 iterations
thread: # executing: select pg_sleep(1)
thread: # executing: select pg_sleep(1)
thread: # executing: select pg_sleep(1)
thread: # executing: select pg_sleep(1)
Multi-threaded: 4.03514003753662s

jmarney:Desktop $ postgres=true async=true ruby db_locking_test.rb

Loading MRI Postgres
Serial: Testing 4 iterations
thread: # executing: select pg_sleep(1)
thread: # executing: select pg_sleep(1)
thread: # executing: select pg_sleep(1)
thread: # executing: select pg_sleep(1)
Serial: 4.02873086929321s
Multi-threaded: Testing 4 iterations
thread: # executing: select pg_sleep(1)
thread: # executing: select pg_sleep(1)
thread: # executing: select pg_sleep(1)
thread: # executing: select pg_sleep(1)
Multi-threaded: 1.02273917198181s

As oldmoe pointed out you have to use the async versions to get async benefits of postgres.

By: roger

roger — Wed, 27 Aug 2008 15:04:00 +0000

Fascinatingly, it appears that the pure ruby mysql driver is also ruby thread friendly. Go figure.

By: Bmore

Bmore — Wed, 27 Aug 2008 15:04:00 +0000

have you guys tried working with a more open mongo table or mongo database like 10gen or something similar to the massive table architecture in google’s app engine?

http://www.10gen.com/

By: Fred

Fred — Sun, 17 Aug 2008 01:06:00 +0000

You should use ruby-mysql 2.7.5

By: Fred

Fred — Sun, 17 Aug 2008 01:06:00 +0000

You should try benchmarking ruby-mysql 2.7.5,
but it still wont solve your concurrency problem,

By: Thomas

Thomas — Sun, 17 Aug 2008 01:06:00 +0000

Ruby 1.9 allows extensions to release the global interpreter lock while they’re performing blocking operations, allowing other threads to run. See rb_thread_blocking_region().

By: Ilya Grigorik

Ilya Grigorik — Sun, 17 Aug 2008 01:06:00 +0000

@Thomas: Ruby 1.8 can do that as well. There are some async client libraries out there, problem is, none of them are production ready.

On the GIL lock.. Ruby is not an exception, Python and most other interpreted languages have the same problem.

By: Lourens Naude

Lourens Naude — Sun, 17 Aug 2008 01:06:00 +0000

Post just been invalidated …

http://github.com/oldmoe/mysqlplus

By: Lourens Naude

Lourens Naude — Sun, 17 Aug 2008 01:06:00 +0000

Post just been invalidated …

http://github.com/oldmoe/mysqlplus