| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The general recommendation for report formatting:[Do not include the section in reports ]
Image wide 1600px. This width offers a good balance, ensuring that images are clear and detailed without causing excessive loading times or appearing too large on the page.
For graphs from AWS CloudWatch use 1 minute metrics aggregation.
...
Attach the link to the report from which the data for comparison was extracted.
Memory Utilization
...
...
Nolana Avg
...
Nolana Min
...
Nolana Max
...
mod-circulation-storage
...
24%
...
23%
...
25%
...
mod-patron-blocks
...
34%
...
33%
...
34%
CPU Utilization
[Description of notable observations of modules and eCPU utilization with screenshots (of all modules and involved modules) and tables]. Annotate graphs to show when a specific test started or ended, and select only the modules that are relevant to the test to show on the graphs]
Memory utilization across all modules was stable, with no memory leaks observed. The most heavily used module, mod-marc-migrations, experienced an increase in memory usage from 25% to approximately 80% during testing with 'Optimal configurations.' However, after the process was completed, memory usage stabilized and returned to normal levels
...
CPU Utilization
CPU utilization during the data-saving process was stable and returned to normal levels after the test was completed. The most utilized service was mod-consortia, with a peak usage of approximately 4.5%. The entire process, including reindexing by mod-search, took approximately 4 hours. With 'Optimal configurations,' the data-saving process was faster by about 1 hour and 30 minutes compared to the default configuration, where it took 2 hours and 40 minutes.
...
Here is the CPU usage of the mod-marc-migrations module during the data-mapping process. It is evident that mod-marc-migrations can handle high loads and return to normal resource usage after the process is completed.
Note: Once the data-mapping process is finished, the CPU usage of mod-marc-migrations becomes less noticeable, as most of the logic for the next step (data saving) occurs on the database side.
...
RDS CPU Utilization
[Description of notable observations of reader and writer instances CPU utilization with screenshots and tables, RDS Database connections, and other Database metrics]
...