We have noticed during review of db query metrics that one particular query which accounts for about 10% of all queries is taking over 95% of the database's time - the count query in searchArtifacts()
We are not even using the outcome of this "count" query, only the results themselves. If the query can't be optimized, maybe a parameter can be added to the search api to skip running this count query?
Description
Registry Version: 2.5.7 Persistence type: sql - postgres 13
We have noticed during review of db query metrics that one particular query which accounts for about 10% of all queries is taking over 95% of the database's time - the count query in searchArtifacts()
https://github.com/Apicurio/apicurio-registry/blob/1b63b543fdff174c1f1e9c20c4840c2c957c77e4/app/src/main/java/io/apicurio/registry/storage/impl/sql/AbstractSqlRegistryStorage.java#L1397
We are not even using the outcome of this "count" query, only the results themselves. If the query can't be optimized, maybe a parameter can be added to the search api to skip running this count query?
Environment
openjdk17 - rhel8
Steps to Reproduce
Expected vs Actual Behaviour
Logs