Skip to content

Explain prerequisites for ETL large memory tweaks option #4906

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
emgcentreon merged 8 commits into from
Dec 23, 2025
Merged

Explain prerequisites for ETL large memory tweaks option #4906

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
e6d6826
Explain prerequisites for ETL large memory tweaks option
emgcentreon Dec 12, 2025
fa9fdd8
Update installation.md
emgcentreon Dec 12, 2025
2af61f7
Update installation.md
emgcentreon Dec 12, 2025
3250238
Apply suggestions from code review
emgcentreon Dec 12, 2025
1283ec5
Update installation.md
emgcentreon Dec 12, 2025
21d9a65
Apply suggestions from code review
emgcentreon Dec 12, 2025
6244acb
Apply suggestions from code review
emgcentreon Dec 23, 2025
2db1989
Apply suggestions from code review
emgcentreon Dec 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion versioned_docs/version-25.10/reporting/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1217,7 +1217,7 @@ Go to **Reporting > Monitoring Business Intelligence > General Options**, **ETL
| **General options** | |
| Reporting engine uses a dedicated dedicated MySQL server | The only appropriate option is **Yes**. |
| Temporary file storage directory on reporting server | Folder where dumps will be stored on the reporting server |
| Use large memory tweaks (store MariaDB temporary tables in memory) | Activated only if your MariaDB configuration and allocated physical memory on the server permit. |
| Use large memory tweaks (store MariaDB temporary tables in memory) | Creates tables using RAM rather than creating them on disk. Not recommended to users who do not have databases with large amounts of RAM (+64GB) |
| **Centile parameters** | |
| Calculating centile aggregation by | Select the desired aggregation level. The standard percentile report provided with BI 2.1 uses Month data. |
| Select service categories to aggregate centile on | Filter on relevant service categories for centile statistics (e.g., Traffic). |
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-26.10/reporting/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1217,7 +1217,7 @@ Go to **Reporting > Monitoring Business Intelligence > General Options**, **ETL
| **General options** | |
| Reporting engine uses a dedicated dedicated MySQL server | The only appropriate option is **Yes**. |
| Temporary file storage directory on reporting server | Folder where dumps will be stored on the reporting server |
| Use large memory tweaks (store MariaDB temporary tables in memory) | Activated only if your MariaDB configuration and allocated physical memory on the server permit. |
| Use large memory tweaks (store MariaDB temporary tables in memory) | Creates tables using RAM rather than creating them on disk. Not recommended to users who do not have databases with large amounts of RAM (+64GB) |
| **Centile parameters** | |
| Calculating centile aggregation by | Select the desired aggregation level. The standard percentile report provided with BI 2.1 uses Month data. |
| Select service categories to aggregate centile on | Filter on relevant service categories for centile statistics (e.g., Traffic). |
Expand Down