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

---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]

Reply via email to