-
Notifications
You must be signed in to change notification settings - Fork 934
Prevent calling UpdateTimesStampsCache for non cached entites #2129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thank you quick reply @hazzik but i think this is not Trivial issue, because when second level cache enabled there is huge performance fall down test could show this. Summary; Oracle Exa Data Database 500 Thread Api Call 2 db read(very little tables), 1 Cache read(Read-Write Cache), 1 insert
2 db read(very little tables), 1 Cache read(Nonstrick Read-Write Cache), 1 insert
|
#2147 should fix that. |
When query cache enabled, I realized that we are storing updatetimestampscache for non cached entities.
Is this really necessary in our scenario we use query cache for just Cache.ReadWrite or Cache.Readonly or Cache.NonstrictReadWrite entities, not non cached entities.
We need high performance to do that we need to decrease Sync. and locking for dml/select operations, its locks all threads in same application its too much cost for per operation.
I think that this needs to be configurable(Store all entities updatetimestampscache or just cacheable entities) or we give us a way to implement our UpdateTimestampsCache, because its readonly?
The text was updated successfully, but these errors were encountered: