similar to: package needed: fastthread-1.0.2

== NOW A new version of fastthread, the library providing better implementations of the classes in thread.rb, has been released. Please note that fastthread is only for Ruby 1.8, not JRuby or any other Ruby implementation (most of them don''t need it anyway!). == WHY The existing implementation of Mutex, Queue, etc. in thread.rb is slow. fastthread''s is faster (and bypasses

I''ve just committed fastthread 0.5.3, which finally gives us a working SizedQueue (which hadn''t really ever worked in previous versions). Mostly it was just a matter of refactoring Queue and SizedQueue into a single class behind the scenes, so I could move the signalling of the SizedQueue-specific condition variable inside the queue''s critical section. Failing to do so

fastthread is a library which replaces the synchronization primitives defined in stdlib?s thread.rb (Mutex, ConditionVariable, Queue, and SizedQueue) with optimized versions which: * are much faster (in the non-contention case, speed comparable to direct use of Thread.critical or Thread.exclusive) * don?t leak memory (the stdlib implementation of Mutex manages to

Heya Folks- This is mainly for Zed and Mentalguy. I have been playing with the new release of rubygems 0.9.0.8 and I have a major problem with the requirement that fastthread needs to be required before thread. Just requiring rubygems and then requiring fastthread right after that will throw the error: ez _blog $ ruby require ''rubygems'' require

Yeah, this is fun! So I''m trying to check a bunch of websites to see if they''ve been updated since the last time I check them. I''m using threads and SizedQueue to grab sets of "feed" objects out of the database, then send them off to be downloaded and compared to existing records. I sometimes get this error, which I don''t understand: [2005-11-04

I just realized -- if fastthread can be included while Mutex-using code is already running, then the definition and replacement of the classes needs to happen atomically. Otherwise, it creates a race condition where a thread can e.g. end up seeing an incompletely defined Mutex class or none at all. fastthread 0.6.1 addresses this by defining the classes and then atomically swapping the constant

Well, just when I thought I was out of the fastthread business... Okay, in brief: fastthread is a Ruby extension which re-implements the primitives in Ruby''s thread.rb in C. It was merged into 1.8.6, replacing the old thread.rb implementation, but the version that was merged had a couple serious bugs. So -- now I release fastthread 1.0, which is basically the Ruby 1.8.6 version with

It looks like I got too creative in 0.6.1 and consequently ran afoul of a bug in the Ruby interpreter. 0.6.2 works around the bug and should be entirely stable at this point. Thanks to Young Hyun for his help in coming up with test cases. == what? fastthread is a Ruby library which provides a faster (and non-memory-leaking) C implementation of the concurrency primitives from stdlib''s

Just a quick note that I''ve committed the bits for fastthread 0.5; the most important differences are that all the thread.rb classes are once again marshallable, and we''ve got Luis'' commit which eliminates some warnings when building on Win32. -mental -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:

I''m confused. Wasn''t threading fixed in 1.8.6, negating the need for fastthread? Why is fastthread still a requirement of Mongrel? Just curious. :)

Hi, A quick search didn''t explain what fastthread is, and how it relates to mongrel. Why would I want to install fastthread? Thanks, Joe

We are trying to use Ruby-ldap 0.9.4 with Ruby 1.84 on Rails 1.1.2. All is running on top of Solaris 2.8. The overall setup works fine for doing other things like access an Oracle DB, and displaying items. When it comes to using Ruby-ldap though, it is quite a different matter. We''ve tried using Ruby-ldap within irb, and all seems well. The basic scenario is: conn =

It looks like fastthread was rolled into 1.8.6: http://svn.ruby-lang.org/cgi-bin/viewvc.cgi/tags/v1_8_6/NEWS?revision=12055&view=markup Does that mean once we upgrade to 186 we can forget about rubygem version? - Rob

Hi All, I have an app making extensive use of Mutex and was concerned about the memory leak I have read about. I saw some sample code to reproduce the problem here: http://pastie.caboo.se/10194 So I thought I would run it myself to see the problem. I do not see a memory leak when using the sample code, but if I require "fastthread" before "thread" using fastthread (0.6.4.1)

Quick note! fastthread 0.6.3 has been released to address a minor compatibility issue with ConditionVariable -- as with the original thread.rb, ConditionVariable can now be used with any mutex class implementing Mutex''s public interface. As before, gem and tarball available from RubyForge courtesy of the Mongrel project: http://rubyforge.org/frs/?group_id=1306 -mental --------------

With Mongrel 0.3.18, I have not seen a single one of the hangs that I have been grousing about for the past N weeks. Thanks MenTaLguY and Zed! Q: Mongrel loads fastthread, Mongrel loads Rails, Rails loads OCI8, OCI8 requires ''thread''. That means OCI8 is using fastthread too, right? Steve

I''ve released fastthread 0.6, which relaxes the order of requires so that fastthread need not be required before thread anymore. Thanks go to Eric and Ezra. -mental -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url :

Hello Guys, Been testing fastthread (known on previous releases as optimized_locking) for soon to be released 0.3.18 mswin32 gems (official ones). Attached to this message is the ruby script I used for the test results shown on graphics [1] and [2] The idea of the script is simulate what Mongrel do with threads creating a simple workload for testing Ruby VM stability. [1] refers to normal,

I was just curious if anyone noticed any significant performance improvements using fastthread (or Ruby 1.8.6) with BackgrounDRb Brandon -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url :

I checked out the latest merb ''trunk'' and after installing it as a gem... (fresh install) I got the dreaded "fastthread not loaded: fastthread must be required before thread" error when starting up an instance of merb. Even without dRB. So I patched the merb.rb file to include fastthread before anything else if it''s installed. Check it. Merry Christmas!