Hi everyone,
I would like to know without any customisation how can a RT instance with
mysql backend can goes.
As I understand it’s the number of tickets who can be a issue.
So…when it’s can become a problem ? 50 000 ? 100 000 ? 500 000 ?
And same question with specific hardware (like mysql on SSD).
Regards.
JAS
Albert SHIH
DIO b�timent 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
T�l�phone : +33 1 45 07 76 26/+33 6 86 69 95 71
xmpp: jas@obspm.fr
Heure local/Local time:
mer 4 nov 2015 22:20:59 CET
1 Like
Hi everyone,
I would like to know without any customisation how can a RT instance with
mysql backend can goes.
We use Pg, but there are places using MySQL that have many tickets.
As I understand it’s the number of tickets who can be a issue.
Perhaps at some very large scale.
So…when it’s can become a problem ? 50 000 ? 100 000 ? 500 000 ?
We run a small instance: ~100,000 tickets in the last 6 or so years.
-m
Le 04/11/2015 � 23:27:53+0100, Torsten Brumm a �crit
Ok, we do around 800.000-1.000.000 Tickets a day. The DB is running since 14 years now. Don’t See Any Problems with such small amount of Tickets.
What ? 1 000 000 tickets per day ? How that’s possible ? …from 14 years ?
that’s mean close to 5 billions tickets ? Hard to belive…
Or do you mean you have 1 000 000 tickets inside your system.
Thanks for your answer.
Regards.
JAS
Albert SHIH
DIO b�timent 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
T�l�phone : +33 1 45 07 76 26/+33 6 86 69 95 71
xmpp: jas@obspm.fr
Heure local/Local time:
jeu 5 nov 2015 00:09:59 CET
Ok, we do around 800.000-1.000.000 Tickets a day. The DB is running since 14 years now. Don’t See Any Problems with such small amount of Tickets.> Am 04.11.2015 um 22:23 schrieb Albert Shih Albert.Shih@obspm.fr:
Hi everyone,
I would like to know without any customisation how can a RT instance with
mysql backend can goes.
As I understand it’s the number of tickets who can be a issue.
So…when it’s can become a problem ? 50 000 ? 100 000 ? 500 000 ?
And same question with specific hardware (like mysql on SSD).
Regards.
JAS
Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71
xmpp: jas@obspm.fr
Heure local/Local time:
mer 4 nov 2015 22:20:59 CET
Hi,
we have over 300000 tickets and process 80000 tickets a year.
We currently use a single VM for our RT (Webserver and Database on the
same Machine).
And our RT is still really fast.
Thanks to the BPS developers.
ChrisAm 04.11.2015 um 22:23 schrieb Albert Shih:
Hi everyone,
I would like to know without any customisation how can a RT instance with
mysql backend can goes.
As I understand it’s the number of tickets who can be a issue.
So…when it’s can become a problem ? 50 000 ? 100 000 ? 500 000 ?
And same question with specific hardware (like mysql on SSD).
Regards.
JAS
Hi everyone,
I would like to know without any customisation how can a RT instance with
mysql backend can goes.
Almost 2 000 000 tickets here (total), mysql DB is about 120GB, two rotational
SATA disks in raid1 array.
As I understand it’s the number of tickets who can be a issue.
For normal usage it works fast. The number of tickets is only a problem for
searching. Here we still use sphinx and searching is quite slow.
The other problem is that any action like searching blocks rt user session
totally. So single user can’t, for example, view other tickets in second
browser tab while his search is in progress. That’s major pain if you do a lot
of searching.
Going to try mysql builtin fulltext next (that won’t fix session problem but
has potential to be faster).
Also for big mysql DB you need to plan backup well.
And same question with specific hardware (like mysql on SSD).
IMO SSD is not required. Obviously will be much faster than rotational disks
but our instance works well without ssd disks.
Regards.
JAS
Albert SHIH
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
Hi JAS,
For normal usage it works fast. The number of tickets is only a problem for
searching. Here we still use sphinx and searching is quite slow.
…
Going to try mysql builtin fulltext next (that won’t fix session problem but
has potential to be faster).
Currently, we are going to setup a system with sphinx & mysql 5.6 because of
the sphinx-fulltext search feature.
So, do you think mysql-5.7 with enabled mysql-fulltext feature is faster?
Can RT use the builtin mysql fulltext search by default without any changes?
Best regards
Danny
smime.p7s (2.23 KB)
Hi JAS,
For normal usage it works fast. The number of tickets is only a problem
for searching. Here we still use sphinx and searching is quite slow.
…
Going to try mysql builtin fulltext next (that won’t fix session problem
but has potential to be faster).
Currently, we are going to setup a system with sphinx & mysql 5.6 because
of the sphinx-fulltext search feature.
So, do you think mysql-5.7 with enabled mysql-fulltext feature is faster?
Why 5.7? For 5.7 is to early to use in production IMO.
I plan to go with 5.6 + fulltext. I didn’t do any measures yet but it should
be on par with sphinx I think. The main advantage of mysql fulltext is that
there is no gap between ticket coming into system and sphinx indexer being
run.
Can RT use the builtin mysql fulltext search by default without any
changes?
It can in recent versions.
sphinx is considered deprecated I think (and buggy; doesn’t make proper sql
queries because mysql optimization engine is allowed to optimize these in such
way that breaks sphinx way of working).
Best regards
Danny
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )