Skip to content
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

View retrieval by key response times #466

Open
pfortin-urbn opened this issue Oct 8, 2024 · 0 comments
Open

View retrieval by key response times #466

pfortin-urbn opened this issue Oct 8, 2024 · 0 comments

Comments

@pfortin-urbn
Copy link

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?!

@pfortin-urbn pfortin-urbn changed the title View retrieval by key response time View retrieval by key response times Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant