SPUG: Shared memory system
dancerboy
dancerboy at strangelight.com
Thu Dec 6 21:39:13 CST 2001
Just a reminder: do a lot of benchmarking/profiling and testing
*before* investing a lot of effort into any performance-improving
scheme. Very often, the bottlenecks in your code are not where you
think they are, and/or your planned optimizations won't end up
improving anything. (E.g. in most cases implementing your own disk
I/O caching is unlikely to improve performance -- and may even make
it worse -- since the OS is doing I/O caching already, and custom
Perl code is unlikely to do it any better.)
(And never, ever forget this maxim: "Premature optimization is the
root of all evil!")
-jason
At 3:49 pm -0800 12/06/2001, Colin Meyer wrote:
>On Thu, Dec 06, 2001 at 02:35:17PM -0800, Peter Darley wrote:
>> Colin,
>> IPC::Shareable seems to be closest to doing what I want; is
>>that included
>> in IPC::Semaphore and it's friends? :)
>
>Yup, IPC::Shareable sits on top of IPC::Semaphore. I do like the interface
>to IPC::Shareable, but don't try to store a "deep" Perl data structure
>with it.
>
>-C.
>
>
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> POST TO: spug-list at pm.org PROBLEMS: owner-spug-list at pm.org
> Subscriptions; Email to majordomo at pm.org: ACTION LIST EMAIL
> Replace ACTION by subscribe or unsubscribe, EMAIL by your Email-address
> For daily traffic, use spug-list for LIST ; for weekly, spug-list-digest
> Seattle Perl Users Group (SPUG) Home Page: http://zipcon.net/spug/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
POST TO: spug-list at pm.org PROBLEMS: owner-spug-list at pm.org
Subscriptions; Email to majordomo at pm.org: ACTION LIST EMAIL
Replace ACTION by subscribe or unsubscribe, EMAIL by your Email-address
For daily traffic, use spug-list for LIST ; for weekly, spug-list-digest
Seattle Perl Users Group (SPUG) Home Page: http://zipcon.net/spug/
More information about the spug-list
mailing list