You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a KTable that contains 980+ million entries in out staging instance - I've create a view over it to be able to extract the ktable data at will. After the initial startup (1.5 hours), I queried the data to checkout the performance and I was surprised at my findings...
If I query data from an entries that was just updated somehow, the response time to retrieve it from the KTable / Local Storage is in the micro-seconds ("duration":"53.122µs") but if I query data that has been at rest in the KTable for 1+ years I get response times in the milliseconds ("duration":"5.095932ms").
I'm wondering why that is, since both entries should come from local key / value storage and I'd expect the same performance for all keys?!
The text was updated successfully, but these errors were encountered:
pfortin-urbn
changed the title
View retrieval by key response time
View retrieval by key response times
Oct 8, 2024
I have a KTable that contains 980+ million entries in out staging instance - I've create a view over it to be able to extract the ktable data at will. After the initial startup (1.5 hours), I queried the data to checkout the performance and I was surprised at my findings...
If I query data from an entries that was just updated somehow, the response time to retrieve it from the KTable / Local Storage is in the micro-seconds (
"duration":"53.122µs"
) but if I query data that has been at rest in the KTable for 1+ years I get response times in the milliseconds ("duration":"5.095932ms"
).I'm wondering why that is, since both entries should come from local key / value storage and I'd expect the same performance for all keys?!
The text was updated successfully, but these errors were encountered: