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

Add a prefetch option to Waltz client #8

Open
whynick1 opened this issue Jul 8, 2019 · 1 comment
Open

Add a prefetch option to Waltz client #8

whynick1 opened this issue Jul 8, 2019 · 1 comment

Comments

@whynick1
Copy link
Contributor

whynick1 commented Jul 8, 2019

Based on PerformanceCli test-consumers performance test, we believe most of the latency in inter-region performance tests are coming from the network hop between regions. The idea is to have the Waltz client add a shouldPrefetch function to the Waltz client requests that will allow the Waltz client internals to evaluate whether a record should be fetched immediately, rather than waiting for the application to call getTransactionData(). Then, when the application does call getTransactionData(), the request is short circuited, and the cached result is returned.

@whynick1
Copy link
Contributor Author

whynick1 commented Jul 8, 2019

shouldPrefetch should probably look something like:

boolean shouldPrefetch(RecordHeader);

patrickghannage pushed a commit that referenced this issue Nov 24, 2020
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