fix(java): skip wasm setResolverState when flag state is unchanged#404
Merged
Merged
Conversation
The periodic state refresh unconditionally pushed the state blob through all wasm pool instances every poll interval (default 15s), even when the state hadn't changed. Each setResolverState call runs wasm execution across all pool slots — expensive CPU work for a no-op when the flag definitions haven't evolved. Compare the new state bytes with the previous via Arrays.equals and skip setResolverState when unchanged. Log flushing still runs every cycle regardless. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
nicklasl
changed the title
andreas-karlsson
approved these changes
May 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The periodic state refresh unconditionally pushed the state blob through all wasm pool instances every poll interval (default 15s), even when the state hadn't changed. Each setResolverState call runs wasm execution across all pool slots — expensive CPU work for a no-op when the flag definitions haven't evolved.
Compare the new state bytes with the previous via Arrays.equals and skip setResolverState when unchanged. Log flushing still runs every cycle regardless.