History.Get endpoint performing poorly

[artrune]

Hello guys, I've been playing with the zabbix API for some time now, the system is growing and the API seems pretty responsive overall except for the history endpoint (Which i believe translates to a backend of 4 MySQL tables)

I'm mainly retrieving 3 days worth of data specifying the time range and the item id (I use this for trends, i want the raw data not the hourly one), but it can take several seconds for the api response to come back. Are there any optimizations I can do somewhere for example in the database (Indexes??)?
Would I get significant performance gains utilizing Timescale over MySQL?

The system has about 700 hosts but there will be more for sure (Storing items 7d/365d)

[LenR]

Have you ran one of the mysql tuner scripts to see what it recommends for your database? We have added a lot of mysql buffer pools. Still, past days history will be "sparse" items from many blocks of db storage so not a good candidate for buffer cache hits anyway. If you haven't done any mysql tuning, you can probably make it better, I'm not sure how much.

The number of hosts is one metric, but more critical is the number of items you are storing per second.

[artrune]

I haven't done any tuning on the MYSQL side (will take a look) and yes probably I could reduce the amount of items but would probably look into optimization like you mentiuon first.
Do you think it'd benefit in any way using timescale?
Thanks for your time