similar to: fastthread 0.5.3

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

I''ve just committed the makings of fastthread-1.0.2 to SVN, fixing a couple long-standing bugs in 1.0.1: - merged the fix from ruby_1_8 to avoid rb_bugging during exit with waiting threads - SizedQueue#enq is now defined properly Could you or whoever does the signed gems please turn the crank and upload the new gems? Thanks, -mental -------------- next part -------------- A

== 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

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

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

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

Hi Is there some definitive guide for upload progress plugin ? We have in this mailing list a lot of testimonials, bug reports, bug fixes, but there are still people like me who cannot use it correctly. Here is my config: - mongrel 1.0RC and upload progress plugin 0.2.1 - a 6 mongrels cluster - config/mongrel_upload_progress.conf: uri "/", :handler =>

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

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''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. :)

I ma trying to get this upload working, http://mongrel.rubyforge.org/docs/upload_progress.html, ....after starting from the command line, mongrel_rails start -d -p 3001 -S config/mongrel_upload_progress.conf I get this eror in the browser, NameError uninitialized constant UploadProgressRailsController RAILS_ROOT: /usr/opt/tomcat/workspace/upload/config/.. Application Trace | Framework Trace

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:

Hi all, I''m using Boxroom (http://boxroom.rubyforge.org/) and trying to get upload progress working. I''ve also been testing the sample code at http://itblog.mcgeecorp.com/2007/5/15/mongrel-upload-progress-demo/. I run a Mongrel cluster, and so am using drb (as per http://mongrel.rubyforge.org/docs/upload_progress.html). Starting up rails, I get lots of useful-sounding output:

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

Hey Zed- I had a user with an app that was leaking memory with mongrel but not lighty/fcgi. I have been doing anything I can to track it down. I already did the Mutex patch to use unshitf and pop instead of shift and push and it didn''t really help much. The mem leak only really shows up when you use the wsess option to httperf. The other day I saw a ruby C extension that

I''m looking for ideas on how you would implement a controller/view in Rails that needs to show the progress of a possibly 2-3 minute operation. For example the user wants to generate 100 reports that will take about 3 minutes. I would like to have a page that would indicate that the operation is taking place as well as showing progress as to how far along. With basic CGI you could

Hello, I''m trying to install the upload_progress gem and i can''t see the upload progress status. My config is : apache2 with mod_proxy mongrel rails upload.rb : ############## require ''rubygems'' require ''drb'' require ''gem_plugin'' GemPlugin::Manager.instance.load ''mongrel'' => GemPlugin::INCLUDE

Hi, I''m having a problem where connections started through BackgrounDRb::MiddleManDRbObject.init are not stopped, resulting in an ever growing established connections between my Mongrels and remote backgroundrbs I added DRb.stop_service to my code executed after requests that init MiddleManDRbObjects but that does not help. Any ideas? Thanks, Robert Bjarnason

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!

Hey Guys, In the readme for Backgroundrb it says that windows support has been depcreated for this version, but then it goes on to mention how to use it in Windows. So I''m not sure if it should be running on windows or not, so I''ll ask anyway. Also, I''m new to ruby and I''m also new to server administration, so I apologize if my questions are pretty