At 00:01 02/07/2003, Jason Greene wrote:
If too many files in a dir became a problem, directory hashing could
easily be implemented into the file based handler.
Too late, it's already in there for a few years :)
Zeev
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: h
Sterling,
you have obviously made up your mind already, so arguing is
moot. Let's have a quick vote and move on.
Pro removing:
Con removing: Sascha
- Sascha
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Having a SQL session storage module in the default
distribution is a good learning example for other storage
module authors. I don't see any necessity to remove this
particular piece of code based on the assessment that it
does not outperform simple file access on Linux. SQLit
On July 1, 2003 04:51 pm, Sterling Hughes wrote:
> So of course we should just say 'screw performance' :) Again, if it
> were useful, I would say "yes, totally." 100% and bucket o' bits. But
> it doesn't give you anything, and it can be in PEAR/PECL for those who
> really want it.
No, I certain
Jason Greene wrote:
Is not a hard cross to bear, and considering that sqlite enabled
sessions should be avoided in the first place, I think its a bad idea to
include them by default.
I still can not see a functionality difference. As to performance, I
think it is obvious that file based sessions ar
>From a performance standpoint you are correct, SQLite looses to files. The
actually performance seems to be quite drastic (very surprising to me). That
said, keep in mind that for most applications even 150 requests/second is an
unattainable limit anyway. For example smarty templating system de
On Tuesday, July 1, 2003, at 04:19 PM, Sterling Hughes wrote:
Sure. But what Wez said was that it only affected you when you got 150
req/s, which is not true. And I am being honest. Over the period of
25000 requests, it is likely that you will have *more* than 300
sessions, not less. This woul
On Tuesday, July 1, 2003, at 04:03 PM, Sterling Hughes wrote:
On Tue, 2003-07-01 at 16:20, George Schlossnagle wrote:
Not really. The slowdown in locking is still there. Its not an across
the board slowdown, but with regards to session handling it is a 1/3
slowdown. What percentage of *total*
On Tuesday, July 1, 2003, at 04:00 PM, Sterling Hughes wrote:
On Tue, 2003-07-01 at 16:15, George Schlossnagle wrote:
On Tuesday, July 1, 2003, at 03:28 PM, Sterling Hughes wrote:
This is no different than a typical mysql setup using myisam
datafiles.
Is mysql session handling bundled? Talkin
On Tuesday, July 1, 2003, at 03:49 PM, Sterling Hughes wrote:
You can't look at raw performance on a simple script in terms of req/s,
but rather percentages. Most scripts are complex, and will have plenty
of other logic in them. Having a 1/3 performance decrement can add up.
This is a completely
On Tuesday, July 1, 2003, at 03:28 PM, Sterling Hughes wrote:
Hi,
Recently sqlite sessions have been added by default. I think this is a
bad idea to have as a default handler. SQLite is not designed for a
write intensive environment, and encouraging such usage seems to be
silly.
SQLite is bad
On Tue, 1 Jul 2003, Sebastian Bergmann wrote:
> Sterling Hughes wrote:
> > It offers not one practical advantage.
>
> I though the same, the SQLite euphoria should not be taken too far.
>
> +1 for removing the SQLite Session Save Handled from the default
> distribution.
-1
Corporate types
Hello Sterling,
Tuesday, July 1, 2003, 9:28:58 PM, you wrote:
SH> Hi,
SH> Recently sqlite sessions have been added by default. I think this is a
SH> bad idea to have as a default handler. SQLite is not designed for a
SH> write intensive environment, and encouraging such usage seems to be
SH> s
Sterling Hughes wrote:
> It offers not one practical advantage.
I though the same, the SQLite euphoria should not be taken too far.
+1 for removing the SQLite Session Save Handled from the default
distribution.
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://p
Sterling, you still seem to be afraid to benchmark sqlite vs mysql or
postgresql sessions.
Also, 150+ req/s is more than most people will ever have hitting their
sites.
Yes, so you fixed some segfaults (are you going to commit that?) but keep in
mind that the code is in the HEAD branch and was on
15 matches
Mail list logo
