Repository navigation
feat(netdata): minimum 768m RAM i 1.0 CPU - #36
Merged
Merged
Conversation
- compose: NETDATA_MEM_LIMIT default 320m -> 768m (CPU default juz 1.0) - configure-resources: staly cap netdaty 768m; CPU_SERVICES dostaje opcjonalne per-usluga minimum (netdata:5:1.0) - na malym hoscie 5% puli dawalo ~0.2 CPU - ensure-config-files: na kazdym `make up` podnosi NETDATA_MEM_LIMIT / NETDATA_CPU_LIMIT ponizej minimum (stare .env maja 320m wpisane przez configure-resources); wyzsze wartosci nietkniete, brak zmiennej = default z compose, niezrozumiala wartosc = ostrzezenie - testy: test_ensure_config_files_netdata_floor + asercje w test_configure_resources - docs: nowe minimum, aktualne sumy RAM (4,3 GB fixed, 5 GB floorow), brakujacy wiersz pgbouncer Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Co
Netdata dostaje minimum 768m RAM i 1.0 CPU — dla nowych i istniejących instalacji.
docker-compose.monitoring.yml:NETDATA_MEM_LIMITdefault320m→768m(CPU default już1.0).scripts/configure-resources.sh: stały cap netdaty 768 MB;CPU_SERVICESma opcjonalne per-usługa minimum (netdata:5:1.0) — na 4-rdzeniowym hoście waga 5% dawała ~0,2 CPU. Kreator odrzuca niższą odpowiedź.scripts/ensure-config-files.sh(każdemake up): podnosiNETDATA_MEM_LIMIT/NETDATA_CPU_LIMITz.env, jeśli są poniżej minimum — stare instalacje mają tam320mwpisane przezconfigure-resources, więc sam default w compose by do nich nie dotarł. Wyższe wartości zostają, brak zmiennej = default z compose, niezrozumiała wartość = ostrzeżenie (bez zmiany).limity-zasobow.md): nowe minimum, zaktualizowane sumy RAM (4,3 GB stałych capów + 5 GB floorów + 2 GB rezerwy ≈ 11,3 GB — minimum 12 GB nadal aktualne, ~0,7 GB nadwyżki), brakujący wierszpgbouncer.Testy
test_ensure_config_files_netdata_floor(320m/0.2 → 768m/1.0; 1g/2.5 bez zmian; brak zmiennych → nic nie dopisane) + asercje wtest_configure_resources.320m→ test czerwony.tmp.XXXXz macOS odrzucana przez compose jako nazwa projektu).mkdocs build --strictOK.🤖 Generated with Claude Code