Improve performance of the /conversations/meta API?

[anirudhsama]

We are using Chatwoot with WhatsApp to manages inbound sales queries. This is slightly different to a traditional support use case where we close conversations. In our use case since its mostly sales, we don't close conversations. This is causing some performance issues, especially with the /conversations/meta API which fetches different counts - count of open conversations, unassigned etc. In our case these numbers would look like 40,000 all conversations, 2000 mine etc. Since these numbers weren't giving us any benefit, we patched the meta API to not query the DB and just return a fixed number of 1 for all counts. This massively reduced the load on the DB. PFA the screenshots.

DB Load:

DB Throughput:

Does it make sense to optimize this API? Perhaps cache the counts?