On Wed, May 23, 2007 4:27 am, Darren Whitlen wrote: > John Comerford wrote: > Not thought about the memory engine actually. Will give that a try and > see how it turns out. Let us know. I'd have GUESSED that MySQL would have just cached something that small and oft-used in RAM anyway, so a MySQL memory engine table wouldn't perform any better than the MySQL half of things. Better than the File System, probably, though that also may be getting cached... > Think I'll leave the session_id idea then, if it locks it down > per-script, the performance will pretty much die. It won't be any better than your own file-system calls, but you could do: <?php session_start(); //read-write $_SESSION here session_write_close(); //don't touch session here ?> And it probably won't be any worse than the locking you presumably already have in your code... WHy is it sometimes MySQL and sometims file system? -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
