Repository navigation
Core: skip OptimaX on page renders when it is off - #1067
Merged
hi-hai merged 1 commit intoOct 16, 2026
Merged
Conversation
The output buffer callback built the Optimax object on every uncached page render. Its constructor reads the litespeed.optimax._summary option, which sites that never used OptimaX do not have, so each render ran one extra SELECT at shutdown and that query appeared in unrelated "Commands out of sync" error logs. Check O_OPTIMAX before building it.
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
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 output buffer callback built the Optimax object on every uncached page render. Its constructor reads the litespeed.optimax._summary option, which sites that never used OptimaX do not have, so each render ran one extra SELECT at shutdown. Unrelated: query appeared in unrelated "Commands out of sync" error logs.