I have a few small, frequently accessed database tables and my goals are: a. Fast access. Which is why I want to have the data loaded in memory. b. Easy access. Having the tables stored in a hash is much more convenient than getting it via DBI or DBM. c. Access from all sessions. As far as I can tell storing the data in the $Application object is the only way to do this.
I've set StateDB to DB_File and it seems to be working fine. This solves problems 'b' and 'c'. I've seen that Berkeley DB has a cache size parameter, so I'm going to see if I can change that and hopefully solve 'a' as well. -----Original Message----- From: Josh Chamas [mailto:[EMAIL PROTECTED] Sent: Thursday, August 19, 2004 4:52 AM To: 'Glen Koundry' Cc: [EMAIL PROTECTED] Subject: Re: Storing large amounts of data in the $Application object Consider also that if you are moving that much data around, then perhaps you are using the $Application / $Session object poorly, with performance in mind. You might redesign your data structures to not require that they be stored fully on disk between requests. Please read about the StateDB config at: http://www.apache-asp.org/config.html#StateDB You can use DB_File or GDBM_File to get faster access to larger data sets for both $Application and $Session. Regards, Josh --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
