Re: collective unconcious (about shared memory...)

in reply to collective unconcious (about shared memory...)

This doesn't answer your question, but...

The customer might well care about resources, but RAM is cheap compared to the time it would take to recode what you've done into C (and then debug it). Unless the customer is deploying this on lots and lots of machines, or unless the cost of taking a server out of production to add RAM is prohibitive, recoding in C might not be such a win.

Comment on Re: collective unconcious (about shared memory...)

Replies are listed 'Best First'.
Re: Re: collective unconcious (about shared memory...) by dshahin (Pilgrim) on Apr 17, 2001 at 03:55 UTC
you're right. But considering how many of these processes might be running simultaneously, I still want to optimize to some degree. I recognize the tradeoff(see original comment) but it is the question of shared memory that may tip the scale in Perl's favor. thanks! plus the client will be running this on every machine...	[reply]

In Section Seekers of Perl Wisdom