> > If you use "File" you may do fine when there are 1000 > files in your sessions directory, but will begin to > degrade speed as it increases. Perhaps there's a > subdirectory, index simulating approach I'm not aware > of. >
Apache::Session doesn't implement such a subdirectory schema, so you really get a lot of files in one directory. This really slows things down, unless you use a filesystem that is able to handle such situation more smart, like ResierFS on Linux does (by using balances trees, instead of doing linear searches in directories) > If you use DB_FIle, does it load the whole file into > memory? I don't know, but you will run into concurrentcy issues, as more as you have a highly loaded server. I don't recommend to use DB_File for session handling, unless you use a DB_File version that can handle concurrent read/write accesses correctly (like the one from sleepy cat, which is not totaly free) > > If you use Mysql, you are really moving a lot of data > around if you're pulling it from a remote server. > Still, it would be quite quick given you have you > sessions table set up optimally. > I think mysql, preferably on the same machine as the webserver, will be (one of) the fastest solutions for highly loaded server. Gerald ------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131 WWW: http://www.ecos.de Fax: +49 6133 925152 ------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
