Skip to main content

Computer Science: More Threads = Less Contention?

Have you read The Next Mainstream Programming Language? The original PDF was written by Tim Sweeney, the founder of Epic, the video game company that created Unreal. He really got me thinking about the problems he was facing.

Let's suppose you have 10,000-100,000 objects. Let's suppose that at any moment any one of them might need to "touch" 50 other objects. That's the setup.

Now, let's suppose that you also have a super-lightweight threading system that can handle 100,000 threads. Yeah, sounds far-fetched, but you'd be surprised. Consider allocating a thread for each object. Along with its own thread, each object should have an input queue into which you can post new events. Naturally, this input queue should be protected by a mutex.

The interesting result is that because there are so many threads trying to access so many mutexes, the chances of any two threads trying to access the same mutex to push a new event is relatively small is you assume a random distribution of events. Practically speaking, more fine grained locking can result in reduced thread contention.

Of course, life isn't random, but it's an interesting thought.


Anonymous said…
I think this is pretty much what ccp games ( is doing. I saw some cool talks about how they are using stackless python to have thousands of threads. Of course they are not exploiting several cores that way, but it shows that the technique can be useful.
Anonymous said…
check out the web server YAWS written in the programming language Erlang.

There are programming models without threads.
jjinux said…
Stackless Python with coroutines is what I was hinting at.
Steve said…
Well, the minute I saw the post I thought "Stackless Python", but I am still trying to understand why you felt it necessary to hint. Why not jusst come out and say what you mean?
jjinux said…
Steve, your question is reasonable. I figured lucky Python people like me weren't the only ones lucky enough to have massively scalable threading systems. I figured the rest of the world would eventually start catching up, so I didn't want to limit the scope of what I was trying to say.
Brandon L. Golm said…
this reminds me of the language I wrote "squirmy" ... it has one thread and one object and can only add two numbers. There's never any contention.
jjinux said…
Squirmy, hmm, I've heard of it. It was interesting in that no one had ever managed to write a buffer overflow or memory leak in that language, right?

I bet if you wrote "Hello World" in Squirmy, it would run *really fast*!

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p