Skip to content

Commit 718c2a9

Browse files
authored
Merge pull request #1670 from netalertx/next_release
Next release
2 parents 01d37fa + 491225d commit 718c2a9

3 files changed

Lines changed: 6 additions & 2 deletions

File tree

docs/PERFORMANCE.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,10 @@ A large database or oversized log files can impact performance. You can check da
2626
> * No table should exceed **10,000 rows** in a healthy system.
2727
> * Actual values vary based on network activity and plugin settings.
2828
29+
Please note that excessively large log files will increase memory consumption. Decrease `MAINT_LOG_LENGTH` if you want to optimize memory use and increase it when debugging issues. See below chart on memory use after logs cleanup.
30+
31+
![memory use after excessive log clean up](./img/PERFORMANCE/logs_memory_usage.png)
32+
2933
---
3034

3135
## Maintenance Plugins
237 KB
Loading

front/plugins/maintenance/config.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -228,7 +228,7 @@
228228
}
229229
]
230230
},
231-
"default_value": 250000,
231+
"default_value": 10000,
232232
"options": [],
233233
"localized": ["name", "description"],
234234
"name": [
@@ -240,7 +240,7 @@
240240
"description": [
241241
{
242242
"language_code": "en_us",
243-
"string": "How many last <code>app.log</code> lines to keep. If <code>LOG_LEVEL</code> is set to <code>debug</code> the app generates about 10000 lines per hour, so when debugging an issue the recommended setting should cover the bug occurence timeframe. For example for a bug with a 3 day periodical appearence the value <code>1000000</code> should be sufficient. Setting this value to <code>1000000</code> generates approximatelly a 50MB <code>app.log</code> file. Set to <code>0</code> to disable log purging."
243+
"string": "How many log entries to keep. When <code>LOG_LEVEL</code> is set to <code>debug</code>, the application generates about 10,000 log entries per hour. Choose a value that covers the expected bug occurrence window. For example, <code>1000000</code> lines (~50 MB) is typically sufficient for issues that occur every 3 days. Set to <code>0</code> to disable log purging. Larger log files increase memory usage, so reduce the value after debugging is complete."
244244
}
245245
]
246246
},

0 commit comments

Comments
 (0)