One more topic regarding performance... in next upcoming OTRS release (not patch level, real feature release) there is also support for persistent caching (currently for local file system, later also for memcached). This is reducing the amount of SQL statements and give a real boost. ;) -Martin On 06.01.2010, at 15:12, Martin Edenhofer wrote:

Hi Alexander,

a) How: You just need to add the modules which are included in the packages like "use Kernel::Module::AgentFAQ;".

b) What is the change: mod_perl will compile all this modules at start time. This means it get used and shard for all httpd processes. Which means it takes less memory for each httpd processes. If you do not use it at start time, every httpd need to compile it, it self.

So IMO it depends on your requirements. If you really need a "faster" system take also a look at http://doc.otrs.org/2.4/en/html/ -> Performance Tuning and/or also the Support-Module is a good point to verify your system settings. IMO this will give you more speed then adding extended modules to startup.pl.

The bad issue is also, if you add your extended modules to startup.pl and you uninstall the package later you will get an httpd error on next startup time (because extended module can not get used).

Just my 2 cents... ;)

-Martin

On 06.01.2010, at 14:59, Alexander Halle wrote:

...

Hello,

does someone know the answer to this old, open question ?

Thanks in advance.

Alexander

-------- Original-Nachricht -------- Date: Tue, 01 Dec 2009 20:39:47 +0100 From: Alexander Halle To: User questions and discussions about OTRS.

Michiel Beijen wrote : [...]

...

Also, in the apache2-perl-startup.pl, you should/could add any modules for packages that you have installed, such as FAQ or ITSM.

Hi Michiel,

I wasn't aware of this yet, I guess it's for speed. Could you please give an example, e.g. for the FAQ module ?

All I could find is an old unanswered posting :

http://lists.otrs.org/pipermail/otrs/2008-August/024183.html

Thanks in advance.

Alexander

-- radprax Gesellschaft fuer medizinische Versorgungszentren mbH, Bergstr. 7 - 9, 42105 Wuppertal, Fon: +49 202 2489 1110, Fax: +49 202 2489 94 1119 Geschaeftsfuehrer: Andreas Martin, Dr. med. Heiner Steffens, Dr. med. Renate Tewaag Amtsgericht Wuppertal: HRB 19359, St.-Nr.: 5132/5889/0264, DE 814559152 Web: http://www.radprax.de

Hi all. Since a couple of days, reaction on the AgentTicketCompose is incredibly slow. It takes between 20 and 40 seconds to load the mail mask after clicking (for example) "empty answer". The phenomenon appeared after a major crash of the file system in which we also lost some of the plain text articles. Maybe there's a relation, maybe not... Any other requests are entirely okay in response, so we're pretty much clueless. System running: OTRS 2.3.3 Debian Linux MySQL 5.0 If someone has a hint... Thanks a lot and a happy new one Daniel

Bingo! Removed the MX Check and it works like charm. The rest will be taken care of later by the linux pros. A bucket of thanks Martin and hope to see you sometimes Daniel Von: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] Im Auftrag von Martin Edenhofer Gesendet: Mittwoch, 6. Januar 2010 19:06 An: User questions and discussions about OTRS. Betreff: Re: [otrs] AgentTicketCompose incredibly slow Hi Daniel, On 06.01.2010, at 16:35, Obee, Daniel wrote: Since a couple of days, reaction on the AgentTicketCompose is incredibly slow. It takes between 20 and 40 seconds to load the mail mask after clicking (for example) "empty answer". The phenomenon appeared after a major crash of the file system in which we also lost some of the plain text articles. Maybe there's a relation, maybe not... Any other requests are entirely okay in response, so we're pretty much clueless. I guess it's not OTRS related. :) Do you know if CheckMX is enabled? In this case OTRS checks the DNS records of the mail exchanger for the recipients (to let the agent know if it's possible to send an email to the recipient). It's configured in SysConfig -> Framework -> Core -> CheckMXRecord. If yes, can it be, that the DNS server which is configured on your OTRS machine is not reachable anymore? In this case OTRS needs to wait for an timeout (it depends on the amount of recipients for each per default about 12 sek.). If it's unix/linux you can verify if DNS is configured correctly by: shell> cat /etc/resolv.conf domain xxx.box nameserver 192.168.178.1 shell> ping 192.168.178.1 64 bytes from 192.168.178.1: icmp_seq=0 ttl=64 time=341 ms [...] shell> host -t mx myhammer.dehttp://myhammer.de/ myhammer.dehttp://myhammer.de/ mail is handled by 10 mx02-berlin.abacho.nethttp://mx02-berlin.abacho.net/. shell> -Martin