similar to: no more wedged mongrels with fastthread

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

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

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

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

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

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

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

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''m running a site that gets ~30k to 40k page hits per day. In the last 4 days my mongrel processes have been jumping into high CPU usage a couple of times a day to the point where my site becomes unresponsive (database on a diff machine with no load). The only way for me to resolve the problem and reduce load on the machine is to delete my rails cache directory (I have plenty of space

I had previously gotten Maik Schmidt''s patch for Oracle working, but now am trying the official Oracle adapter with the latest Rails. I''ve been trying to get the OCI8 connector to install under OS X, but get the following error. Has anyone gotten it working? ---- [waterdog:~/Desktop/ruby-oci8-0.1.9] stmpjmpr% ruby setup.rb config ---> lib ---> lib/DBD ---> lib/DBD/OCI8

Hello Everyone, We''re hard at work getting the hot new win32 service Luis wrote out and ready for production. We''re hoping to have that included in the 1.0 RC1 release we make very soon. This pre-release is just to make sure that we didn''t step on any toes. Install it with: $ gem install fastthread --source=http://mongrel.rubyforge.org/releases $ gem install

Hi all, I am strangely getting errors on Debian Etch on a Intel server though I had done an identical install of mongrel-1.0.1 on an amd64 version of Etch. While building fastthreads I get: ERROR: While executing gem ... (Gem::Installer::ExtensionBuildError) ERROR: Failed to build gem native extension. ruby extconf.rb install mongrel creating Makefile make gcc -I.

My company''s System-admin installed Ruby and Gems (using Sun Coolstack package) and I have sudo access to ruby, gem etc. Now I need to get my app to talk to oracle db (through network). From what I understand, it requires three steps: Step 1: Install oracle instant client ( I installed it in my ~/oracle/ instantclient_11_1) Step2: Install OCI8 libraries (this is where I am stuck). Here is

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)

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

All of a sudden, on three different systems, the "server_ip_address/sid_name" syntax in database.yml has stopped working for me. I can''t even do a OCI8.new(blah blah blah) statement from an IRB shell. I get "ORA-12541: TNS:no listener", or some variant, depending on how I phrase it. On systems where I have a real deal client installed, and OCI can find the tnsnames

Hi folks, Does anyone know how to install the OCI8 ruby interface on Debian64 without having to install Oracle? My understanding, from experience with Debian i386, is that you need Oracle (specifically the SQLPlus) installed to be able to compile OCI8. Since my new dev machine is AMD64 running Debian, I''m stuck. My rails applications need to connect to a remote Oracle 10g, but cannot