]
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
To: Sean Chittenden [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: mod_perl shared memory with MM
Sean,
Yeah, I was thinking about something like that at first, but I've never played
with named
At 22:23 Uhr -0500 10.3.2001, DeWitt Clinton wrote:
On Sat, Mar 10, 2001 at 04:35:02PM -0800, Perrin Harkins wrote:
Christian Jaeger wrote:
Yes, it uses a separate file for each variable. This way also locking
is solved, each variable has it's own file lock.
You should take a look at
On Sun, Mar 11, 2001 at 03:33:12PM +0100, Christian Jaeger wrote:
I've looked at Cache::FileCache now and think it's (currently) not
possible to use for IPC::FsSharevars:
I really miss locking capabilities. Imagine a script that reads a
value at the beginning of a request and writes it
I'm very intrigued by your thinking on locking. I had never
considered the transaction based approach to caching you are referring
to. I'll take this up privately with you, because we've strayed far
off the mod_perl topic, although I find it fascinating.
One more suggestion before you take
DeWitt Clinton wrote:
On Sun, Mar 11, 2001 at 03:33:12PM +0100, Christian Jaeger wrote:
I've looked at Cache::FileCache now and think it's (currently) not
possible to use for IPC::FsSharevars:
I really miss locking capabilities. Imagine a script that reads a
value at the beginning
Can I ask why you are not useing IPC::Sharedlight (as its pure C and
apparently much faster than IPC::Shareable - I've never benchmarked it
as I've also used IPC::Sharedlight).
Full circle back to the original topic...
IPC::MM is implemented in C and offers an actual hash interface backed by
Perrin Harkins wrote:
Can I ask why you are not useing IPC::Sharedlight (as its pure C and
apparently much faster than IPC::Shareable - I've never benchmarked it
as I've also used IPC::Sharedlight).
Full circle back to the original topic...
IPC::MM is implemented in C and offers an
On Sat, 10 Mar 2001, Christian Jaeger wrote:
For all of you trying to share session information efficently my
IPC::FsSharevars module might be the right thing. I wrote it after
having considered all the other solutions. It uses the file system
directly (no BDB/etc. overhead) and provides
At 0:23 Uhr -0800 10.3.2001, Perrin Harkins wrote:
On Sat, 10 Mar 2001, Christian Jaeger wrote:
For all of you trying to share session information efficently my
IPC::FsSharevars module might be the right thing. I wrote it after
having considered all the other solutions. It uses the file
Christian Jaeger wrote:
Yes, it uses a separate file for each variable. This way also locking
is solved, each variable has it's own file lock.
You should take a look at DeWitt Clinton's Cache::FileCache module,
announced on this list. It might make sense to merge your work into
that module,
On Sat, Mar 10, 2001 at 04:35:02PM -0800, Perrin Harkins wrote:
Christian Jaeger wrote:
Yes, it uses a separate file for each variable. This way also locking
is solved, each variable has it's own file lock.
You should take a look at DeWitt Clinton's Cache::FileCache module,
announced on
I have some preliminary benchmark code -- only good for relative
benchmarking, but it is a start. I'd be happy to post the results
here if people are interested.
Please do.
- Perrin
For all of you trying to share session information efficently my
IPC::FsSharevars module might be the right thing. I wrote it after
having considered all the other solutions. It uses the file system
directly (no BDB/etc. overhead) and provides sophisticated locking
(even different variables
Adi Fairbank wrote:
Yeah, I was thinking about something like that at first, but I've never played
with named pipes, and it didn't sound too safe after reading the perlipc man
page. What do you use, Perl open() calls, IPC::Open2/3, IPC::ChildSafe, or
IPC:ChildSafe is a good module, I use it
Sean Chittenden wrote:
Is there a way you can do that without using Storable?
Right after I sent the message, I was thinking to myself that same
question... If I extended IPC::MM, how could I get it to be any
faster than Storable already is?
You can also read in the data
Adi Fairbank wrote:
I am trying to squeeze more performance out of my persistent session cache. In
my application, the Storable image size of my sessions can grow upwards of
100-200K. It can take on the order of 200ms for Storable to deserialize and
serialize this on my (lousy) hardware.
Is there a way you can do that without using Storable?
Right after I sent the message, I was thinking to myself that same
question... If I extended IPC::MM, how could I get it to be any
faster than Storable already is?
You can also read in the data you want in a startup.pl file
; Linux 2.2.14-5.0 i586)
X-Accept-Language: en
To: Sean Chittenden [EMAIL PROTECTED]
Subject: Re: mod_perl shared memory with MM
It's ok, I do that a lot, too. Usually right after I click "Send" is when I
realize I forgot something or didn't think it through all the way. :)
Sean
Sean,
Yeah, I was thinking about something like that at first, but I've never played
with named pipes, and it didn't sound too safe after reading the perlipc man
page. What do you use, Perl open() calls, IPC::Open2/3, IPC::ChildSafe, or
something else? How stable has it been for you? I just
I am trying to squeeze more performance out of my persistent session cache. In
my application, the Storable image size of my sessions can grow upwards of
100-200K. It can take on the order of 200ms for Storable to deserialize and
serialize this on my (lousy) hardware.
I'm looking at RSE's MM
Adi Fairbank wrote:
I am trying to squeeze more performance out of my persistent session cache. In
my application, the Storable image size of my sessions can grow upwards of
100-200K. It can take on the order of 200ms for Storable to deserialize and
serialize this on my (lousy) hardware.
Perrin Harkins wrote:
Adi Fairbank wrote:
I am trying to squeeze more performance out of my persistent session cache. In
my application, the Storable image size of my sessions can grow upwards of
100-200K. It can take on the order of 200ms for Storable to deserialize and
serialize
22 matches
Mail list logo
