[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Erik de Castro Lopo <mle+ocaml@m...> |
| Subject: | Re: [Caml-list] forking, threads and events |
skaller wrote: > The correct way to do this is one pthread per CPU (called a > worker thread) and use fibres (synchronous threads) within > those pthreads. Then you will need a thread for I/O. > > You really should use Felix. I'm pushing for Ocaml on this project. If that doesn't fit the bill there are others in the team pushing for Erlang. > If you don't need performance .. why did you mention using > multiple cores? One core will do. I'm trying to optimize performance of lots of small sub-processes which are likely to block on I/O. I'm therefore trying to start as many as possible simultaneously rather than run them one by one serially. > Felix runs on Win32 using any C++ compiler, including MSVC++ > and uses the native Win32 API. It's currently not only > the logical choice for high performance high level asynchronous > programming .. its also the ONLY choice I have been led to believe that Erlang also fits the bill. > unless you count C++ as 'high level' :) I call C++ a curse on programmers everywhere; the language that has enabled and encouraged more stupidity and bad software design than any other programming language ever. Erik -- +-----------------------------------------------------------+ Erik de Castro Lopo +-----------------------------------------------------------+ "It is forbidden for a Muslim to be a loyal friend to someone who does not believe in God and His Prophet, or someone who fights the religion of Islam." -- Fifth grade text book from Saudi Arabia http://www.washingtonpost.com/wp-dyn/content/article/2006/05/19/AR2006051901769_pf.html