Displaying 4 results from an estimated 4 matches for "rb_thread_select".
2007 Jun 19
1
fastthread errors on Debian Etch
...error: expected declaration
specifiers or ''...'' before ''fd_set''
/usr/lib/ruby/1.8/i486-linux/intern.h:216: warning: ''struct timeval''
declared inside parameter list
/usr/lib/ruby/1.8/i486-linux/intern.h:216: error: conflicting types
for ''rb_thread_select''
/usr/lib/ruby/1.8/i486-linux/intern.h:216: error: previous declaration
of ''rb_thread_select'' was here
/usr/lib/ruby/1.8/i486-linux/intern.h:217: warning: ''struct timeval''
declared inside parameter list
/usr/lib/ruby/1.8/i486-linux/intern.h:217: error: c...
2012 Nov 07
1
select(): Interrupted system call from curb when stopping unicorn
Hi,
We''ve just migrated one of our rails applications from nginx/passenger
running on REE 1.8.7 Ubuntu 8.04 to unicorn running on MRI 1.9.3 on
Ubuntu 10.04. The app makes a number of calls to internal services
using curb.
Our deployment script stops unicorn by sending SIGQUIT to the unicorn
master, sleeps for a few seconds to ensure that HAProxy has taken the
node out of service and
2007 Dec 14
21
Some silly benchs (was: 1.9)
Guys,
Just for fun, I tried to see (I know, a silly way to test it) how much
overhead we have calling the C functions of the extensions.
the benchmark script and the results:
http://pastie.caboo.se/128646
The naive C extension:
http://pastie.caboo.se/128647
I compared 1.8.6 (VC6 and mingw builds) against a fresh checkout of ruby trunk.
What I understand from that is 1.9 is slower than 1.8
2007 Dec 25
30
Review of Code for 1.9
Hello Guys,
I''m reviewing the code for 1.9, and forgot about this when we first
spoke on this subject.
The current way we stop threads is using Thread#raise to spread
StopServer exception, which will not work as expected in 1.9.
1.9 will treat raised exceptions as #kill, like JRuby does, so the
worker threads will not finish serving the client and _then_ exiting,
but will be