Running osTicket 1.9.2 on a fancy host with lots of resources, yada, yada, yada.
24,200+ tickets in the database. At last check the database had grown to 2.6GB.
After several hours of inactivity I can log in to check the tickets, wait a few seconds to see the open ticket list, pick a ticket and then wait another 15-30 seconds before seeing the ticket details. Once I see the first ticket, everything seems pretty fast.
Can't help but think that data has expired in a cache and that's when I get to twiddle my thumbs waiting for everything to reload. When I complain to my host, all is working fine because I had recently checked things.
Are there and parameters to tweak for something like this?
Will there ever be a way to move tickets to an archive for slow access to speed up the main database for active items?