Comments on: Threading models: So many different ways to get stuff done. http://timetobleed.com/threading-models-so-many-different-ways-to-get-stuff-done/ technical ramblings from a wanna-be unix dinosaur Wed, 21 Jul 2010 07:31:26 +0000 hourly 1 http://wordpress.org/?v=3.0 By: ice799 http://timetobleed.com/threading-models-so-many-different-ways-to-get-stuff-done/comment-page-1/#comment-377 ice799 Sat, 27 Jun 2009 04:56:12 +0000 http://timetobleed.com/?p=57#comment-377 Perhaps you could explain how you'd implement a simple userland package that takes advantage of multiple cores? Perhaps you could explain how you'd implement a simple userland package that takes advantage of multiple cores?

]]> By: Guest http://timetobleed.com/threading-models-so-many-different-ways-to-get-stuff-done/comment-page-1/#comment-375 Guest Fri, 26 Jun 2009 20:15:23 +0000 http://timetobleed.com/?p=57#comment-375 Can you explain the threading models a little more? For example, I can write a simple userland package which takes advantage of multiple cores, but blocking calls will block the kernel thread and until the blocking call completes there's one less core available to run the program. Thus, it looks like it sits kinda half-way between 1:N and M:N. Can you explain the threading models a little more? For example, I can write a simple userland package which takes advantage of multiple cores, but blocking calls will block the kernel thread and until the blocking call completes there's one less core available to run the program. Thus, it looks like it sits kinda half-way between 1:N and M:N.

]]> By: Renato http://timetobleed.com/threading-models-so-many-different-ways-to-get-stuff-done/comment-page-1/#comment-368 Renato Thu, 21 May 2009 19:33:52 +0000 http://timetobleed.com/?p=57#comment-368 Fantastic! <br><br>I've been looking for an explanation that is short and informative like this (I'm a n00b in this area...) for quite some time.<br><br>This should go straight to Wikipedia. :) Fantastic!

I've been looking for an explanation that is short and informative like this (I'm a n00b in this area…) for quite some time.

This should go straight to Wikipedia. :)

]]> By: Fixing Threads in Ruby 1.8: A 2-10x performance boost at time to bleed by Joe Damato http://timetobleed.com/threading-models-so-many-different-ways-to-get-stuff-done/comment-page-1/#comment-348 Fixing Threads in Ruby 1.8: A 2-10x performance boost at time to bleed by Joe Damato Mon, 18 May 2009 10:01:35 +0000 http://timetobleed.com/?p=57#comment-348 [...] threads, also known as “green threads.” (Want to know more about threading models? See this post.) The major performance killer in Ruby’s implementation of green threads is that the entire [...] [...] threads, also known as “green threads.” (Want to know more about threading models? See this post.) The major performance killer in Ruby’s implementation of green threads is that the entire [...]

]]> By: New Engine for Booko at Booko’s Blogo http://timetobleed.com/threading-models-so-many-different-ways-to-get-stuff-done/comment-page-1/#comment-341 New Engine for Booko at Booko’s Blogo Mon, 11 May 2009 11:32:16 +0000 http://timetobleed.com/?p=57#comment-341 [...] that JRuby may in fact be the best way to run this type of code.  Ruby 1.8’s threading model blocks on I/O - not great for my price grabber. The solution is pretty easy though - just run multiple price [...] [...] that JRuby may in fact be the best way to run this type of code.  Ruby 1.8’s threading model blocks on I/O – not great for my price grabber. The solution is pretty easy though – just run multiple price [...]

]]> By: 6 Line EventMachine Bugfix = 2x faster GC, +1300% requests/sec at time to bleed by Joe Damato http://timetobleed.com/threading-models-so-many-different-ways-to-get-stuff-done/comment-page-1/#comment-273 6 Line EventMachine Bugfix = 2x faster GC, +1300% requests/sec at time to bleed by Joe Damato Wed, 29 Apr 2009 19:33:32 +0000 http://timetobleed.com/?p=57#comment-273 [...] On top of all that, this patch helps with Ruby’s green threads, too. If the epoll_wait causes a Ruby event to fire and that event creates a Ruby thread, that Ruby thread gets an entire copy of the existing stack. Each time that thread is switched into and out of, that thread stack has to be memcpy’d into and out of place. Reducing those memcpys by ~800,000 bytes is a HUGE performance win. Want to learn more about threading implementations? Check out my threading models post: here. [...] [...] On top of all that, this patch helps with Ruby’s green threads, too. If the epoll_wait causes a Ruby event to fire and that event creates a Ruby thread, that Ruby thread gets an entire copy of the existing stack. Each time that thread is switched into and out of, that thread stack has to be memcpy’d into and out of place. Reducing those memcpys by ~800,000 bytes is a HUGE performance win. Want to learn more about threading implementations? Check out my threading models post: here. [...]

]]> By: cg http://timetobleed.com/threading-models-so-many-different-ways-to-get-stuff-done/comment-page-1/#comment-170 cg Mon, 01 Dec 2008 11:38:25 +0000 http://timetobleed.com/?p=57#comment-170 Nice post explaining all the pros and cons of various threading models .. Nice post explaining all the pros and cons of various threading models ..

]]> By: I/O models: how you move your data matters at time to bleed http://timetobleed.com/threading-models-so-many-different-ways-to-get-stuff-done/comment-page-1/#comment-84 I/O models: how you move your data matters at time to bleed Mon, 27 Oct 2008 14:05:43 +0000 http://timetobleed.com/?p=57#comment-84 [...] this blog post I’m going to follow suit on my threading models post (here) and talk about different types of I/O, how they work, and when you might want to consider using [...] [...] this blog post I’m going to follow suit on my threading models post (here) and talk about different types of I/O, how they work, and when you might want to consider using [...]

]]>