2012/5/14 Michiel Beijen michiel.beijen@otrs.com:
Hi Edwind,
Edwind Richzendy Contreras Soto schreef op 2012-05-14 07:15:
- It is appropriate to have so many services? (I did not do the
configuration of OTRS)
Most organizations use less services, typically between 50 and 100, but sometimes also more.
- why are so many queries to the database?
- that information is not stored in cache to make selection faster
then?
OTRS 3.1.3 and up (tomorrow we'll release 3.1.5) will use much less queries to the database; it will use much more caching.
I updated to version 3.1.4 and in fact performance drastically change that view now takes a second or less.
I'll wait until tomorrow to leave the new version for testing and update with that.
thank you very much
What also might help is if you do not store sessions in the database, but on the file system (see Core::Session under Admin > SysConfig > Framework).
I will try this also does not hurt to optimize a bit more performance
- If I type ACL Queue-> Services [2], the charging time will be
faster service? and related services only appear to the queue defined in the ACL? 5) as I can make the load time of service is much faster?
The strange thing is that the queries in your database do not take the most time, right? They all execute in the same second, apparently. It might be interesting, using a profiler, to learn where your system is spending this much time: in the database, or maybe in the application logic. If you want, you can install 'Fred' - a helper tool for OTRS development - from here:
http://ftp.otrs.org/pub/otrs/develtools/packages/Fred-3.1.2.opm
it features Devel::NYTProf integration, so you can analyze exactly what is happening. Of course you should only want to install Fred on a dev machine, NOT on production! -- Mike
OTRS mailing list: itsm - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/itsm To unsubscribe: http://lists.otrs.org/mailman/listinfo/itsm