[SOLVED] Clarification on Switching Ticket Backend Docs

[interploy]

Hello,

I just wanted to get some clarification on the performance tuning documentation about switching ticket index backends.

Reference: http://otrs.github.io/doc/manual/admin/ ... uning.html

My OTRS database is getting fairly large (a sql dump file is 9.6GB). The ticket table is getting close to passing 77,000 rows. I see in the documentation that it recommends switching backends from Kernel::System::Ticket::IndexAccelerator::RuntimeDB (what I have currently) over to Kernel::System::Ticket::IndexAccelerator::StaticDB when OTRS has more than 80,000 open tickets.

My question is this: When the documentation states 80k open tickets, is it referring to actual open tickets (as in, being actively worked on) or the total number of tickets in the system (77k in this case)? For all of the tickets in the database, users typically only have around 100-150 tickets actively being worked on at any given time. The rest are closed, but are used in reports.

Thanks for any insight,
-interploy

[crythias]

I could be wrong, but I would take it to mean open ever, or just *tickets*.

[interploy]

I could be wrong, but I would take it to mean open ever, or just *tickets*.

That's where I was leaning, but I wanted to make sure. I've lost count of the number of times I've bungled code because of an assumption. :lol:

Thanks for the input!

[dim3nsi0n]

Hello,

I'm a newbie as well
Even though the ticket is marked as SOLVED I am still confused....
We have around 100k tickets in our database but less than 6000 open tickets the rest are closed or archived. Should we use StaticDB or RuntimeDB?

Thank you!
Andrei

[interploy]

Hello,

I'm a newbie as well :)
Even though the ticket is marked as SOLVED I am still confused.... :?
We have around 100k tickets in our database but less than 6000 open tickets the rest are closed or archived. Should we use StaticDB or RuntimeDB?

Thank you!
Andrei

Hi Andrei,

To clarify, the documentation is referring the to the total number of tickets in the database and not just the ones that are currently active. At 100k entries, you should consider switching the backend to StaticDB if you see your system's performance start suffering.

Hope that helps,
-interploy

[dim3nsi0n]

Thank you so much for your quick answer!