(continuing investigations) I tried to investigate -d:DProf, but could not run a search with DProf.
opac-main.pl page profiling with Dprof give this result: Total Elapsed Time = 1.573963 Seconds User+System Time = 1.503963 Seconds Exclusive Times %Time ExclSec CumulS #Calls sec/call Csec/c Name 15.2 0.229 0.348 24 0.0096 0.0145 XML::LibXML::_parse_sax_file 7.85 0.118 0.160 2496 0.0000 0.0001 XML::Simple::collapse 5.32 0.080 0.768 10 0.0080 0.0768 C4::Overdues::BEGIN 3.99 0.060 0.060 17 0.0035 0.0035 utf8::SWASHNEW 3.66 0.055 0.055 4776 0.0000 0.0000 XML::Simple::characters 3.32 0.050 0.069 7 0.0071 0.0099 XML::LibXML::SAX::BEGIN 3.32 0.050 0.099 15 0.0033 0.0066 C4::Context::BEGIN 2.66 0.040 1.191 11 0.0036 0.1083 C4::Auth::BEGIN 2.66 0.040 0.040 74 0.0005 0.0005 Exporter::export 2.59 0.039 0.039 556 0.0001 0.0001 DBI::st::execute 1.99 0.030 0.195 6 0.0050 0.0325 C4::Heading::BEGIN 1.99 0.030 0.529 9 0.0033 0.0588 C4::Reserves::BEGIN 1.99 0.030 1.350 9 0.0033 0.1500 main::BEGIN 1.99 0.030 0.059 197 0.0002 0.0003 Exporter::import 1.93 0.029 0.056 615 0.0000 0.0001 DBI::_new_sth 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. -- Frédéric _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel