(RADIATOR) threading

[Ingvar Berg (LI/EAB)]

> -----Original Message-----
> From: Rodrigo Nuno Bragança da Cunha
> 
> Thread creation in perl is much slower than forking. I've also seen 
> great improvments just by replacing ithreads with the 
> forks.pm module... 
> and less bugs... and MUCH less memory consumption (yes, incredible).

The solution should be to have a definable number of threads chewing the input queue, so they are created at startup. Maybe you would like to have a min/max number of threads, but I don't really think so "A good server is memory-resident".
And memory consumption isn't always an issue.

/Ingvar (adding my SEK 0.02)
> 
> Given the current state of perl native threads if you really need the 
> threads model you should try forks.pm, or else live with fork alone.
> 
> Andy De Petter wrote:
> 
> >
> > PS: I don't agree in the fact that you say that threading won't 
> > necessarily improve anything. Threads tend to be much faster to 
> > create, and use less memory than forked processes. I agree, perl 
> > doesn't fully take advantage of this yet, but they will 
> once - and we 
> > should better be ready for it. ;)
> >
> 
> --
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.
> 

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.