Correct me if I'm wrong but I fear that a huge amount of time is burnt just reading Koha XML config file (do you see anything else?) Koha config file being an XML file is a good thing. It's not even a problem if reading XML file in Perl is slow (could be for MARC records). But this file shouldn't be read over and over. It should be an application-level information loaded only once at Koha application startup. Same applies for sysprefs, even if it seems not to have the same incidence on performances.
So we come back to mod_perl which allow to define global (application/session) variables.
Or memcached which allows us to cache the entire conf file as an object and access it that way. Ditto with the system preferences. Or indeed both memcached and mod_perl :) Chris _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel