Zabbix 6.0 startup speed up

[supafly]

Is there any way to speed up zabbix 6.0 startup procedure?
Like hot configuration cache?
I have a relatively large config — about 10G. Restart alone can take up to 10 minutes. Yes, there are a couple of slow queries — selects from items and items_discovery tables.
In that time proxies hold their caches, and dumping cache on server as it starts, it can take 10-20 minutes. Because of that delay triggers that are too sensitive firing and can create mini alert storm.
History syncers starts only after configuration syncer, that is a significant delay. Why waste time waiting for configuration sync if you can write some historic data in that period.
Startup procedure is the same in newer versions?

[Viktors Fomics]

Hello

Since you are mentioning slow queries it might be reasonable to review those, maybe adding some additional indexes could be useful.

Additionally I'd suggest taking a look at your CacheSize parameter, for such a large config it might need to be increased.

[cyber]

Additionally I'd suggest taking a look at your CacheSize parameter, for such a large config it might need to be increased.

If it runs out of it, server crashes..

I have cacheSize also set to 10G. But it never causes such issue. Yes, I do see some slow queries and history syncer is busy for a while.. but never config syncer...

[supafly]

Hello

Since you are mentioning slow queries it might be reasonable to review those, maybe adding some additional indexes could be useful.

Additionally I'd suggest taking a look at your CacheSize parameter, for such a large config it might need to be increased.

I don’t know that much about indexing, so I’m open for suggestions. I assumed that the indices included in the standard scheme should have been sufficient. It seems that this is not the case, I guess.
Also, my config cache at 20G right now. And servers uses about 45% of it.

[supafly]

I have cacheSize also set to 10G. But it never causes such issue. Yes, I do see some slow queries and history syncer is busy for a while.. but never config syncer...

In my case config syncer 100% during startup and spikes up to 100% every configuration sync for couple of minutes, but it doesn’t effect server performance.
For the history syncer is the same for startup since it is trying to shove all the data from proxies to a database. During normal operations history syncer utilized for 10-15%.
So the question is how to optimize initialization of server, since all other processes works as intended.
Is there any “best practices” for this kind of problem?