There's your problem right there. MySQL performs badly. I'm getting max 3s for these operations where you get ~7-8s and that's in a VM, on Windows.
You need to install a private MySQL instance for OTRS, on the same machine where the rest of OTRS components are installed (server 2: otrs, apache+modperl). I'm quite sure this will solve your performance problems. On Tue, May 13, 2014 at 5:08 PM, Mimiko <vbv...@gmail.com> wrote: > SQL Benchmar results: > > Result: SQL > KEY VALUE TIME COMMENT > Insert Time: 10000 8 s :-( Should not take more than 5's on > an average system. > Update Time: 10000 7 s Ok > Select Time: 10000 7 s :-( Should not take more than 6's on > an average system. > Delete Time: 10000 4 s :-) Looks fine! > Multiplier: * 1 s > > ---------------------------------------------------------------- > Result: SQL > KEY VALUE TIME COMMENT > Insert Time: 50000 24 s Ok > Update Time: 50000 27 s Ok > Select Time: 50000 30 s Ok > Delete Time: 50000 24 s Ok > Multiplier: * 5 s > > > The overall report loads fast. Its all green, meaning ok. Except some log > warnings. > > Well, server 1: Mysql, VoIP, Apache+PHP. > server 2: otrs, apache+modperl > > > > > On 13.05.2014 16:52, Bogdan Iosif wrote: > >> There's a package named Support that you should install from Package >> Manager. After it's installed you'll have a new link in the ADMIN page, >> named Support Assessment. Follow the link to a page presenting a report >> about the environment OTRS is running on. The report may load VERY >> slowly and return timeouts. Keep retrying. When it finally succeeds, go >> through it and beware of any anomalies as they may clue you into why >> you're having problems. >> >> Additionally, notice that on the Support Assessment page you have a link >> in the upper left named SQL benchmark. Follow the link to a page from >> which you can run a benchmark on the database. This will help evidencing >> if there are issues for OTRS with the connection between the web server >> and the db server. >> >> If I understood things correctly, you have the db server on a dedicated >> machine (call it dbsrv-machine) but you run the VoIP server on the same >> machine as OTRS (call it websrv-machine). In this case, an additional >> thing to check would be if the Apache instance running OTRS is starved >> for resources (memory, etc.). >> > > > -- > Mimiko desu. > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs >
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
