Subj : Re: Futexes are wrong! (Are they?)
To   : comp.programming.threads
From : Jomu
Date : Wed Jun 15 2005 04:58 pm

And you are very selective in replying :).

As I say, and I will repeat this last time in this thread - landscape
is moving. What was unthinkable five years ago, works today. 10,000
threads running on home PC is piece of cake now, impossible five years
ago. Even more efficient synchronization is being developed and spread
as we talk.

I would think about exact way of solving 10k client when I need it -
for hundreds and up to few thousands I feel no drawbacks of t-p-c
approach - my programs work and they are almost under noticeable on
common PC. For 10k I will probably need some auxiliary level for
serialization of requests for some specific resources, but context
switch is surely nothing to be afraid, anymore. And it would be even
less noticeable as time passess.

And "thread is personification of client" (in t-p-c) is something I
really like as it helps me, and other people
reading/perusing/justenjoying my code to understand/maintain/extend
what I wrote. If you need your "one advantage", think about that. Think
about plainly writing what you really need to be done, not multiplexing
it in some event driven interface. No select, no pool, kqueue, epoll...
just simple blocking I/O ;). How's that about
compatibility-over-various-platforms? One concept which works
everywhere, same - blocking I/O :).

And, as I said.. I am lookig forward to see you in t-p-c as it becomes
more and more O(1) all around :).

dd

.