Date: Thu, 28 Mar 2024 14:46:16 +0000 (UTC) Message-ID: <2146399686.3886.1711637176171@skald.opmantek.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3885_1453716394.1711637176171" ------=_Part_3885_1453716394.1711637176171 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
opReports 3.1.10 introduce= s a newly developed known_reports_cache to speed up the loading of reports:
When the known_re=
ports_cache is enabled and one deletes generated reports via =
the commandline or in a cron job, it is necessary to update the =
known_reports_cache flag files modified time=
to flag that the cache must refresh - this command will suffice:
Flushing the cache with th= e above command is safe and may also be useful in problem-solving.= strong>
The performance of the opR= eports known_reports_cache can be summarised as follows, when checked on a = virtual server with 4 CPUs , 16GB of RAM, not using any swap, and with 2.7G= B size of /path/to/omk/var/ directory:
opReports Page Loaded | Time to load without known_reports_cache (second= s) | Time to load with known_reports_cache (seconds)<= /th> |
---|---|---|
Dashboard | 15.53 | 16.52 |
Operational Status | 40.27 | 15.36 |
Report Schedules | 17.56 | 3.29 |
Saved Reports | 26.01 | 13.48 |
Opening grouped_capacity Report within Saved Rep= orts Page | 864 | 25.23 |
On-Demand Reports | 18.24 | 3.33 |
Opening grouped_capacity Report within On-Demand= Reports Page | 954 | 25.43 |