Hello,
we have a few years of tickets stored in MySQL database, in MyISAM tables.
Last few weeks the OTRS is becoming slow. I feel it could be caused by
using MyISAM tables since locking is working at table level, while with
InnoDB it's done at row level.
OTOH, the InnoDB tables do not support fulltext searching.
Could anyone tell me if it's worth moving tables to InnoDB and which tables
should be moved, or, which should be left in MyISAM?
Thank you
MyISAM tables, slow OTRS, better InnoDB ?
Moderator: crythias
-
- Znuny superhero
- Posts: 723
- Joined: 10 Oct 2007, 14:30
- Znuny Version: 3.0
- Location: Hamburg, Germany
Re: MyISAM tables, slow OTRS, better InnoDB ?
I´d never give advice on systems I have never seen.
You say, that you have years of tickets in your system, but it performs slower for a couple of weeks. I would look for the problem in some other direction, but not at that point.
Have a look at mysqltuner.pl to tune your database. It does not make everything perfect, but its a good point to start with.
Please fill your signature!
You say, that you have years of tickets in your system, but it performs slower for a couple of weeks. I would look for the problem in some other direction, but not at that point.
Have a look at mysqltuner.pl to tune your database. It does not make everything perfect, but its a good point to start with.
Please fill your signature!
openSuSE on ESX
IT-Helpdesk: OTRS 3.0
Customer Service: OTRS 3.0 (upgraded from 2.3)
Customer Service (subsidiary): OTRS 3.0
+additional test and development systems
IT-Helpdesk: OTRS 3.0
Customer Service: OTRS 3.0 (upgraded from 2.3)
Customer Service (subsidiary): OTRS 3.0
+additional test and development systems