On Thu, 16 Jun 2005, Jim Gallacher wrote:
Also I think it's worth the time to squeeze as much performance out of
mod_python as is possible.
+1 on that!
Grisha
Right, I was thinking the same thing... those are pretty extreme
conditions. But very interesting as a benchmark. I assume ext3?
Nick
dharana wrote:
Wow, good work Jim.
A bit of perspective:
5 active sessions with an average of 15 mins duration per session
means roughly 4,800,000 requ
Nick wrote:
Right, I was thinking the same thing... those are pretty extreme
conditions. But very interesting as a benchmark. I assume ext3?
Yes. It would be interesting to see the same thing on ReiserFS or JFS,
but that will have to wait for another day.
dharana wrote:
Wow, good work J
Wow, good work Jim.
A bit of perspective:
5 active sessions with an average of 15 mins duration per session means
roughly 4,800,000 requests a day or 55 requests per second.
Jim Gallacher wrote:
Hello All,
In testing the new req.get_session() method for the upcoming 3.2.0
release I've
Hello All,
In testing the new req.get_session() method for the upcoming 3.2.0
release I've noticed that the performance of FileSession degrades badly
as number of session files rises. Assuming this is related to putting a
large number of files in a single directory, I decided to do some
bench
Nicolas Lehuen wrote:
Is there a way to forbid PythonSessionOption from appearing in a
.htaccess file ?
I don't know. Is there a way to restrict the use of any Python*
directives? Or to restrict the use of AddHandler mod_python? These
restrictions would be useful in a shared hosting environm
Is there a way to forbid PythonSessionOption from appearing in a
.htaccess file ? If not, then there is no advantage (security-wise) in
having a different configuration directive.
But your point about not breaking existing code is a good one. If
someone already uses "PythonOption session*" directi
