mirror of
https://github.com/ClusterCockpit/cc-backend
synced 2026-03-24 00:27:29 +01:00
Checkpoint: 52552d244fc5
Entire-Session: 50b2b10a-1be0-441f-aafb-3c5828f0fcc9 Entire-Strategy: manual-commit Entire-Agent: Claude Code Ephemeral-branch: entire/eba3995-e3b0c4
This commit is contained in:
26
52/552d244fc5/0/context.md
Normal file
26
52/552d244fc5/0/context.md
Normal file
@@ -0,0 +1,26 @@
|
||||
# Session Context
|
||||
|
||||
## User Prompts
|
||||
|
||||
### Prompt 1
|
||||
|
||||
Implement the following plan:
|
||||
|
||||
# Make SQLite Memory Limits Configurable via config.json
|
||||
|
||||
## Context
|
||||
|
||||
Fixes 1-4 for the SQLite memory leak are already implemented on this branch. The hardcoded defaults (200MB cache per connection, 1GB soft heap limit) are conservative. On the production server with 512GB RAM, these could be tuned higher for better query performance. Additionally, `RepositoryConfig` and `SetConfig()` exist but are **never wired up** — there's currently no way to override any re...
|
||||
|
||||
### Prompt 2
|
||||
|
||||
Also add a section in the README.md discussing and documenting the new db options.
|
||||
|
||||
### Prompt 3
|
||||
|
||||
Why is the option cache-size-mb set to DB size / max-open-connections and not to DB size. Why does this allow to hold the complete DB in memory when the cache size is smaller than the total DB?
|
||||
|
||||
### Prompt 4
|
||||
|
||||
Yes please add a clarification to the README
|
||||
|
||||
Reference in New Issue
Block a user