Abhijeetsng97 opened a new issue, #13573: URL: https://github.com/apache/gravitino/issues/13573
### What would you like to be improved? When entity caching is disabled (gravitino.cache.enabled=false), Gravitino uses NoOpsCache, which acquires a single shared lock for all entity reads. The lock remains held during database access, forcing unrelated reads to execute sequentially. Under concurrent load, this slows down metadata reads and increases request latency. A slow database lookup blocks other requests, potentially exhausting request threads and causing timeouts. Since NoOpsCache stores no cached state, this locking is unnecessary. Reads should execute concurrently when caching is disabled. ### How should we improve? _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
