If you are running a busy site that stores a fair amount of data, what would the best choice be for session storage? I want to know from people who have applied knowledge of this. I guess theoretical ideas would have value too.
I'm thinking there'd be trade-offs in whatever you choose. 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. If you use DB_FIle, does it load the whole file into memory? Of course, this would become quite a challenge to your server as the number of entries/unique user sessions increase. I guess it doesn't have to load it into memory, but I wonder if it does. 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 have not looked into the other choices, such as FileFile and so on. Please let me know any thoughts you might have on this. -Jarrod __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
