FYI-- here are some Apache::Session benchmark results. As with all
benchmarks, this may not be applicable to you.
Thanks for taking the time to run these and write up the results.
Benchmark: This benchmark measures the time taken to do a create/read for
1000 sessions. It does not destroy
Question: does anyone know how to pre-specify the _session_id for the
session, rather than allowing Apache::Session to set it and read it? I
saw
some posts about it a while back, but no code...
Isn't it just this?
tie %session, 'Apache::Session::Foobar', $id;
That only works if the
Gerald Richter sent the following bits through the ether:
That only works if the session id already exists. If the session id doesn't
exists, Apache::Session will throw an exception (die)
The documentation implies that is it currently possible to do so. I'd
love for it to be possible to do
Gerald Richter sent the following bits through the ether:
That only works if the session id already exists. If the session id
doesn't
exists, Apache::Session will throw an exception (die)
The documentation implies that is it currently possible to do so.
But the perl code shows that it
Perrin Harkins wrote:
Apache::Session::File - Dual-PIII-600/512MB/Linux 2.2.14SMP: Ran 4
times.
First time: ~2.2s. Second time: ~5.0s. Third time: ~8.4s. Fourth time:
~12.2s.
Is there any reason not to use a file tree approach (splitting first and
second characters of filenames into
On Wed, 13 Dec 2000, Jeremy Howard wrote:
Perrin Harkins wrote:
Apache::Session::File - Dual-PIII-600/512MB/Linux 2.2.14SMP: Ran 4
times.
First time: ~2.2s. Second time: ~5.0s. Third time: ~8.4s. Fourth time:
~12.2s.
Is there any reason not to use a file tree approach (splitting
FYI-- here are some Apache::Session benchmark results. As with all
benchmarks, this may not be applicable to you.
Basically, though, the results show that you really ought to use a database
to back your session stores if you run a high-volume site.
Benchmark: This benchmark measures the time
