That is a little smaller than my primary production site which has 22500 tickets, 2GB database (which includes attachments).
I do not consider it much.
mLipok Any ideas on how to improve the speed of operation.
Will separating saving attachments to files instead of to the database help?
Separating the attachments from the DB will reduce DB size. Smaller DBs are traditionally faster. It could help, but honestly I cannot quantify by how much. If your database server is already well optimized, has plenty of hardware resources, etc. then it will likely not have much of an impact. That being said it should help.
mLipok Maybe it was affected because I have "Never cleanup logs",
And it works in such ways from 2014....
Honestly, you probably do not need to do anything with this at all. Although I personally do not see the point in keeping logs that long. Changing to 3 months would likely reduce the size of the database once those logs get purged. (see comment about smaller DBs being faster above). I do not think that you will notice a difference from this, but I could be wrong.
mLipok If I switch to storing files as files (not in data base) what will happend ?
All already saved files in DB will be migrated to files system as files, or will stay in DB ?
What If I decide to switch back from FileSystem to DB ?
This depends on you.
If you just switch to storing file on the filesystem... then all new attachments will be stored on the filesystem.
This will also slow the growth of the database.
If you switch to storing files on the filesystem AND migrate your attachments in the DB to the filesystem then new attachments will be stored on the file system and all your old ones will to. This would probably be your biggest bang for your buck when it comes to reducing the size of your database. [read this as: you will likely notice a speed difference doing this.]
When it comes to performance there is tuning that you can do on the server side (note: you likely cannot do MySQL tuning if your using a cheap web host. How to do MySQL/MariaDB server speed tuning is a bit beyond the support that we provide here on the forum.
There are a couple things that you can likely do yourself such as converting your DB tables to the InnoDB engine instead of MyISAM.
See Dev post here:
https://forum.osticket.com/d/99249-performance-tuning/2
You can look at the MySQL slow query logs and see what queries are causing things to be slow. These can be reported to the devs and they might be able to do something about it.
If a ticket action (assign / transfer / etc) generates an email, this can also slow things down if the time to connect to the mailserver and send the message takes a long time. This like setting up an on prem mail relay server, or using the webhosts mail server can speed this up by reducing network latency, etc.
