Are cached KV values in local DCs evicted earlier than the specified TTL if they are infrequently re
Are cached KV values in local DCs evicted earlier than the specified TTL if they are infrequently read?
cacheTtl parameter, then yes. It is best effort, which means that it will, at the most, be cached for the specified amount of time
cacheTtl, based on demand/other factors
I'm assuming locations for KV are same as cache and D1 locations are lot fewer.KV has two central stores and can be cached in every location.
metadata so it could be fetched during the list operation when the item data is small otherwise I still have to manually get each item out of KV.UID:SID as the key lets me use prefix to list a user's sessions, but I cant query a session by just having the session ID (without the user id)SID as the key lets me query sessions with just a session ID, but I dont know how to list a user's sessions.SID key and UID value, and if I need to list a user's sessions I just list every session and filter it in the code itself. This seems a bit weird though cause if I have thousands of sessions this may slow things down
SID, and UID:SID. SID stores the actual session data, and UID:SID doesn't actually store anything, but just allows you to list through a user's Sessions