|
Caching is the obvious best bet I think.
If you manage updates to the permissions through the same system you can force
cache updates using it so your system would effectively have real-time data.
Generally anything that can cut down on DB hits in CF is a good thing since a
good chucnk of the problems seen seem to stem form the database drivers and
DB-related memory leaks. Another option, depending on your
database, would be to streamline your calls. Most modern DBMSs can do recursive
calls to themselves – using that your “100 database calls”
could be turned into one call which returned permissions for the entire
ancestry line. Even with optimized calls a lot of calls means network and CF
overhead for the call, the instantiation and parsing of CFQUERY objects and so
forth. Reducing the process to a single database call could speed things up a
lot. Jim Davis |
- RE: [CFCDev] Speeding up lookups in a chain Jim Davis
- Re: [CFCDev] Speeding up lookups in a chain Barney Boisvert
- RE: [CFCDev] Speeding up lookups in a chain Kwang Suh
- RE: [CFCDev] Speeding up lookups in a chain Kevin J. Miller
- RE: [CFCDev] Speeding up lookups in a chain Kevin J. Miller
- RE: [CFCDev] Speeding up lookups in a chain Micha Schopman
- Re: [CFCDev] Speeding up lookups in a chain Barney Boisvert
- [CFCDev] OT: Laszlo Brent Nicholas
- Re: [CFCDev] OT: Laszlo Scott Stroz
- Re: [CFCDev] OT: Laszlo Adam Haskell
