feat: Add support for an SQLite cache as a low-memory option - #14
Merged
Merged
Conversation
aklinker1
added this pull request to stack #16
October 1, 2026 22:44
Member
Author
|
Didn't really help, went right back up after loading the WXT homepage. 
I think the memory usage comes from the dataloader cache. Will remove from there, or follow their advice and create an instance per-request. 
|
Member
Author
|
Oh, but it's not permanent like before... interesting. after a few minutes memory usage went down, until I loaded wxt.dev again. 
That means it could just be the number of HTML pages I'm holding in memory while crawling everything. The data loader just stores some small JSON snippets. I should fix that bug, but that's definitely not the main problem. |
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
1 participant
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 service is dying all the time because it's running on a 1 vCPU, 1GB RAM machine. Instead of upgrading and paying more, I'm going to move the cache into SQLite so it uses disk space (which I have a lot of) instead of memory.
The process runs OOM, an new one is started, and it loops. Each color is a different container.
The type of cache is controlled by env vars, so I'll post resullts after it's been released.
Also, thrown errors are now cached and rethrown for the TTL. Before, if there was an error, it would try to fetch the latest value again and fail again, which is slow.