Hi Eric,
What do you think of this (about fulcrum security objects mapped with hibernate) :
- using lazy instanciation for collections is a good choice
- but initializing every Set (GroupSet, UserSet, ...) in each SecurityEntity just after an entity is loaded (as this is done in User, Group and Role) seems to make the "lazy" configuration useless
don't you think it can lead to performance hits ? (just look at the number of sql queries generated)
Mike
Eric Pugh wrote:
Use the HibernateSecurityService in Fulcrum. Hibernate has very comprehensive caching, and there is an adapter so you can use it with Turbine 2.3. Check out the unit tests for Fulcrum Security for examples.
Eric
-----Original Message----- From: Edmund Urbani [mailto:[EMAIL PROTECTED] Sent: Friday, March 05, 2004 3:50 PM To: [EMAIL PROTECTED] Subject: Acl and TorqueSecurityService (Turbine 2.3)
Hi!
I was trying to speed up my webapp, so I let torque log all the sql queries (log level "debug") to identify the performance bottleneck(s). It seems I am getting a huge amount of queries on the TURBINE_ROLE, TURBINE_PERMISSION and TURBINE_GROUP tables for every single http request. I have lots of hasRole(..), hasPermission(..) calls to the AccessControllList which appear to be causing this. Is there a way to make the ACL/TorqueSecurityService keep/cache more data in memory?
I am going to look deeper into this. Maybe I will end up writing my own subclass of the TorqueSecurityService, that does have some options for caching... (or has anyone done that already?)
Edmund
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
