Re: [Phplib-users] Sessions in text files

[Layne W. <la...@dr...>]

Hristo Odiseev wrote:

> My last experience was that the last time I did a repair I got a 11MB
> table (before repair - 233MB). As you see that is really a problem.
> And if I don't do anything the table grows to 2Gb which is really an
> overkill for mysql. But that was just some background info.

That sounds like a serious problem. If you haven't spent money on
professional MySQL support yet, you probably should try to find some budget
funds to do so.

> Why do you think that the I/O will become a problem? Could you give
> me some reasoning? I guess that the size of the sessions will not be
> so big as it is in the DB. At current its extreme size is mostly due
> to the corrupted data.

The last time (February or March of this year) that I looked into switching
to session4.inc, I started reading the PHP manual comments on PHP 4 native
sessions. Several people mentioned that they sped up their busy sites and
reduced server disk I/O by using a database handler for PHP 4 sessions
instead of the default file handler. After reading that, I abandoned
implementing PHP 4 native sessions and kept using classic PHPLib sessions.

I took a chance and trusted the manual comments so I don't have any persona=
l
experience to back up the assertion.

--=20

Layne Weathers