On 02/12/12 14:08 +0100, Albert Cervera i Areny wrote: > Some conclusions: > - With PostgreSQL, speedup is even higher than my first numbers if no strange > default_get() issues are involved. > - With PostgreSQL, even if the main bottle neck with current implementation > is > addressed by the multiple inserts (simpler) implementation, there's still > room > for improvement using a single insert (92% instead of 77% speedup).
I still prefer the simpler implementation. Moreover the code of complex will be more complex to handle my concern about length of query. > - We should find a solution for singletons when there's no record so we can > still use the cache. It could be possible to cache the default_get method but I'm not sure it is a correct solution. I think it is better to say, you have to create the singleton. Also I think it is the Property field that are slow and they should be replace by explicit Function field using a new table with real foreign key. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpCgdlALsjJv.pgp
Description: PGP signature
