Want this feature implemented? Please upvote! Posts in this thread won't be published. Read Me!

User Story

As a PRTG User, Administrator and System Engineer I want more performance

Details of User Story

Installations above 15000 sensors are getting so slow in the WebUI. Modifications are even slower and take ages. Config File gets bloated (+1GB XML)

So maybe split the Config File into one for Systemkonfiguration and one for each probe where the monitoring configuration resides Also split up the parts from the Core. Webserver, DB Server, konfiguration Server, Reporting and so on all in one Box cant scale well.

Give the customers above 10000 sensors the ability to scale well without the need to deploy more separate PRTG Instances.

Acceptance criteria

  • Split Core Application in at least 2 components: 1.) Webserver 2.) DB Server
  • Split the config file so that the server does not need to write a whole 1GB+ File each time it gets saved and improve modification time
  • Reduce overall (performance) impact of reporting, while improving reporting performance in itself. We need to be able to get a separate reporting instance, or, be able to export the data to MS SQL.

Status

Looking At.

Article Comments

This has been partially adressed with PRTG 19.1.48:

PRTG Core ServerThis version includes various minor and major performance improvements, especially for the handling of a lot of remote probes. We also improved the scalability of the server with CPU cores and memory, the server startup times, and the post-processing of configuration changes (special thanks to electromichi for pointing us to this issue!).

Feb, 2019 - Permalink