Re^3: Approaches to concurrency

Replies are listed 'Best First'.
Re^4: Approaches to concurrency by JavaFan (Canon) on Feb 09, 2009 at 15:16 UTC
Nevertheless, most Linux distros come with a threaded perl these days. Of course. Otherwise, they'll have to field complaints that threaded applications won't work. Whenever distro makers have to make a choice of "going for performance" or "going for broadest usage", they'll pick most of the times the latter. That will be more useful for most of their users, and hence, themselves. Having said that, I often compile my own perls. On my home boxes, and on all work boxes where perl performance, version, and/or configuration is important.	[reply]
Re^4: Approaches to concurrency by BrowserUk (Patriarch) on Feb 09, 2009 at 14:48 UTC
the difference was about 15%. That's the figure I vaguely remember from 5.6.1 vs. 5.6.2 days. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]
Re^4: Approaches to concurrency by wazoox (Prior) on Feb 12, 2009 at 12:34 UTC
I think Slackware was the last to do the switch. I'm pretty sure that Slack's perl wasn't threaded at least up to Slack 10.x.	[reply]