PLATFORM - Administration > Administrator Guide > Repositories > Repository Performance and Health
Repository Performance and Health
Consulting Repository Performance
Before you start working in an RDBMS repository, MEGA recommends that you run the RDBMS diagnostic utility (available in the MEGA store: store.mega.com).
*For more details on this utility, see the deployment guide: Installation and Deployment > RDBMS Repository Installation Guide.
This utility indicates repository performance compared to optimized performance.
Generating a Repository Health Report
With HOPEX you can generate a daily RDBMS repository health report. This report enables to detect:
performance or usage anomalies that users can face daily.
any significant change.
For this purpose, performance and health tests are run daily. Events are generated when anomalies are detected.
*See Event Supervision Description > Repository Health Technical Article.
Performance test description
HOPEX standard use scenarios are performed every afternoon ("RepositoryHeath Daily Afternoon Trigger” job, 04:00 pm GMT):
Reading of comments on read-only data (“Reading of”).
Read-only data loading.
Request execution on read-only data.
Comment writing on reading and writing data.
Data creation.
Data deletion.
Search request execution on reading and writing data.
*In a cluster-type configuration, performances are measured on all of the machines.
Each scenario generates a result, which is stored in the repository. These results are analyzed daily in the evening ("RepositoryHeath Daily Evening Post Trigger” job, 11:05 pm GMT)
An history of 36 results are needed before generating an alert.
Health test description
It is essential to analyze certain usages to identify anything that might compromise data integrity, whether in the daily work or following a HOPEX update.
For all of the repositories of all of the environments, the following checks are performed every evening ("RepositoryHeath Daily Evening Trigger” job, 11:00 pm):
Administration
SQL compatibility of repositories and server
table fragmentation
index fragmentation
SQL maintenance plan execution
Customization
HOPEX data modification
HOPEX data volume
Usage
workspace volume
*In a cluster-type configuration, usage tests are performed randomly on a single machine only.
Health report description
The health report includes a short description of the anomaly detected at performance or usage level.
For example, in case of an index fragmentation anomaly:
Sent from: <Name of the machine that ran the report formatting and emailing task>
Environment: <Environment name>
Repository: <Repository name>
Table A_BLOB
Index GBM_INDEX_A_BLOB_IDABS_BEGIN_VALIDITY
Fragmentation level 70%
Configuring HOPEX health report emailing
*HOPEX health reports, automatically generated every day, are available from HOPEX Administration desktop, see Viewing the HOPEX Health Reports.
You can receive a short report of all of the anomalies detected on each repository of each environment.
The HOPEX health report is emailed daily (by default):
You must check that the mailing configuration parameters are configured (in the site level options).
You must define the list of recipients of the report.
You can modify the report receiving frequency.
E.g.: Daily, Weekly (Sunday), Daily (working days), Monthly (1st day of the month).
To configure HOPEX for emailing its health report:
1. Access the site level options.
2. Check the mailing configuration parameters:
In the Options tree, select Installation > Electronic Mail folder.
In the right pane, check that the mailing configuration parameters are specified.
Example:
Default address of author via SMTP (FROM): admin@domain.com
SMTP Server: mail.server.domain.com
SMTP Port: 25
3. Define the recipients of the report:
In the Options tree, select Repository > Repository Health folder.
In the field of the Repository Health Report: recipients option, enter the email of the recipient of the HOPEX health reports.
*You can enter several recipients (the separating character is the coma: ",").
E.g. : dan.woods@mega.com,julia.perri@mega.com
4. (If needed) For the Repository Health Report: frequency option, use the drop-down menu to modify the report receiving frequency.
E.g.: Daily (working days)
The recipients of the report receive an email at the frequency defined, showing a summary and including the attached detailed report.