Comments on: Socket Timeouts in Ruby http://www.mikeperham.com/2009/03/15/socket-timeouts-in-ruby/ On Ruby, software and the Internet Wed, 21 Jul 2010 20:03:10 -0500 http://wordpress.org/?v=2.9.2 hourly 1 By: sergeych http://www.mikeperham.com/2009/03/15/socket-timeouts-in-ruby/comment-page-1/#comment-445 sergeych Sun, 08 Nov 2009 03:07:56 +0000 http://www.mikeperham.com/?p=220#comment-445 doesn't work on Mac OS 10.5/ruby1.9. Does anybody ever wrote a decent sockets lib interface? Maybe everybody use dl direct calls for real work? Sockets in ruby, even 1.9, looks more like a joke... doesn’t work on Mac OS 10.5/ruby1.9. Does anybody ever wrote a decent sockets lib interface? Maybe everybody use dl direct calls for real work? Sockets in ruby, even 1.9, looks more like a joke…

]]> By: Rodjer http://www.mikeperham.com/2009/03/15/socket-timeouts-in-ruby/comment-page-1/#comment-376 Rodjer Tue, 16 Jun 2009 07:37:32 +0000 http://www.mikeperham.com/?p=220#comment-376 Mike, any impression on how memcache client fares against memcached? While the memcache gem is certainly more managable and well supported in eg. Rails and related projects, then libmemcached appears to be the C lib that gets the most love. Any thoughts on where we're headed and on the pros/cons of either library? Thanks Mike, any impression on how memcache client fares against memcached?

While the memcache gem is certainly more managable and well supported in eg. Rails and related projects, then libmemcached appears to be the C lib that gets the most love.

Any thoughts on where we’re headed and on the pros/cons of either library?

Thanks

]]> By: mperham http://www.mikeperham.com/2009/03/15/socket-timeouts-in-ruby/comment-page-1/#comment-365 mperham Sat, 06 Jun 2009 19:10:17 +0000 http://www.mikeperham.com/?p=220#comment-365 @cheapRoc, memcache-client is designed to work on all ruby platforms. It's included with Rails and so compatibility is the #1 priority. If you need absolute maximum speed, you should upgrade to fauna/memcached, which in my experience is extremely fast but difficult to use on anything but Linux. And, as Aaron has proven, often Ruby can be made quite fast without sacrificing compatibility if you know what you are doing. Thanks Aaron! @cheapRoc, memcache-client is designed to work on all ruby platforms. It’s included with Rails and so compatibility is the #1 priority.

If you need absolute maximum speed, you should upgrade to fauna/memcached, which in my experience is extremely fast but difficult to use on anything but Linux.

And, as Aaron has proven, often Ruby can be made quite fast without sacrificing compatibility if you know what you are doing. Thanks Aaron!

]]> By: Aaron Patterson http://www.mikeperham.com/2009/03/15/socket-timeouts-in-ruby/comment-page-1/#comment-364 Aaron Patterson Sat, 06 Jun 2009 18:42:03 +0000 http://www.mikeperham.com/?p=220#comment-364 Hi! I patched memcache-client to make it fast by using a buffered IO object and non-blocking reads. I think it will work on all platforms. Bonus is that you don't need SystemTimer at all. Here are my benchmarks: http://gist.github.com/124957 Here is my patch: http://github.com/tenderlove/memcache-client/commit/5d7f38ca066fcc9059432186d15c8fc50fcdfbcf Oh, I sent a pull request too. :-) Hi! I patched memcache-client to make it fast by using a buffered IO object and non-blocking reads. I think it will work on all platforms. Bonus is that you don’t need SystemTimer at all.

Here are my benchmarks:

http://gist.github.com/124957

Here is my patch:

http://github.com/tenderlove/memcache-client/commit/5d7f38ca066fcc9059432186d15c8fc50fcdfbcf

Oh, I sent a pull request too. :-)

]]> By: cheapRoc http://www.mikeperham.com/2009/03/15/socket-timeouts-in-ruby/comment-page-1/#comment-363 cheapRoc Sat, 06 Jun 2009 16:37:26 +0000 http://www.mikeperham.com/?p=220#comment-363 @mperham excellent, excellent article and code. one question though, i don't seem to understand rolling back features just because all platforms do not support them. shouldn't the features that we implement be tailored to each platform, utilizing the best that they provide, not dulling them down by spreading basic functionality across all of them... personally, i completely ignore Windows all together because i'm not best fit to provide that Windows support. the power of OSS compels you. ;) @mperham excellent, excellent article and code.

one question though, i don’t seem to understand rolling back features just because all platforms do not support them.

shouldn’t the features that we implement be tailored to each platform, utilizing the best that they provide, not dulling them down by spreading basic functionality across all of them…

personally, i completely ignore Windows all together because i’m not best fit to provide that Windows support. the power of OSS compels you. ;)

]]> By: mperham http://www.mikeperham.com/2009/03/15/socket-timeouts-in-ruby/comment-page-1/#comment-362 mperham Sat, 06 Jun 2009 13:41:14 +0000 http://www.mikeperham.com/?p=220#comment-362 raggi, the benchmark is part of the test suite in the memcache-client source at http://github.com/mperham/memcache-client And as an update, I've had to roll back any use of socket timeouts in Ruby. They don't work on all platforms (like Solaris mentioned above). raggi, the benchmark is part of the test suite in the memcache-client source at http://github.com/mperham/memcache-client

And as an update, I’ve had to roll back any use of socket timeouts in Ruby. They don’t work on all platforms (like Solaris mentioned above).

]]> By: raggi http://www.mikeperham.com/2009/03/15/socket-timeouts-in-ruby/comment-page-1/#comment-361 raggi Sat, 06 Jun 2009 11:12:27 +0000 http://www.mikeperham.com/?p=220#comment-361 What was the benchmark, and why is there such a massive discrepancy? Just because timeout is broken in it's capabilities, I can't see why it would be over 200% slower. What was the benchmark, and why is there such a massive discrepancy?

Just because timeout is broken in it’s capabilities, I can’t see why it would be over 200% slower.

]]> By: David R http://www.mikeperham.com/2009/03/15/socket-timeouts-in-ruby/comment-page-1/#comment-329 David R Sun, 12 Apr 2009 23:16:43 +0000 http://www.mikeperham.com/?p=220#comment-329 Apparently SO_RCVTIMEO/SO_SNDTIMEO are not supported in solaris, which renders the most recent version of the memcache-client pretty impotent. I am getting these errors: Errno::ENOPROTOOPT: Option not supported by protocol And some googling on SO_RCVTIMEO and solaris didn't come up with any great solutions. Apparently SO_RCVTIMEO/SO_SNDTIMEO are not supported in solaris, which renders the most recent version of the memcache-client pretty impotent. I am getting these errors:

Errno::ENOPROTOOPT: Option not supported by protocol

And some googling on SO_RCVTIMEO and solaris didn’t come up with any great solutions.

]]> By: Dmytro Shteflyuk http://www.mikeperham.com/2009/03/15/socket-timeouts-in-ruby/comment-page-1/#comment-322 Dmytro Shteflyuk Wed, 25 Mar 2009 15:56:41 +0000 http://www.mikeperham.com/?p=220#comment-322 Hey Mike, Thanking you for the great sharing! I was looking for some technique to handle timeouts in my Sphinx ruby client for a long time. Currently we (Scribd) wrap all calls in SystemTimer blocks, but your solution is much cleaner and it would be great improvement. Keep up your good work. PS. We are using your memcache-client too and really enjoyed it. You rock! Hey Mike,

Thanking you for the great sharing! I was looking for some technique to handle timeouts in my Sphinx ruby client for a long time. Currently we (Scribd) wrap all calls in SystemTimer blocks, but your solution is much cleaner and it would be great improvement. Keep up your good work.

PS. We are using your memcache-client too and really enjoyed it. You rock!

]]>