Performance

The performance of this plugin is mainly dependent on:

• The performance/response time of the catalog, which is highly dependent on the size of it, the underlying filesystem and the configuration at the database level

• The number of daemons (Storage Daemons, File Daemons) available in the environment

• The configured services to be executed

• The load of the host at the moment of BGuardian execution

In summary, it is not possible to establish an exact reference about how much time the daemon execution will take to complete. It usually should take some minutes to complete. However, there are some services that will take significant time to complete if the catalog is very large as the implied queries are heavy. These services are ‘deviation’ and, specially, ‘orphanchain’. If there are some services taking too long, it is possible to define different parameters for different executions of the service. For example, we can run a set of services daily or even hourly, while running different services once a week. This is easily set up by using different AdminJobs with command line parameters, testing different services, and then associating them with different schedules.

The general recommendation is to run the daemon once a day over a time window where the load of the backup environment is low. Following this principle, it should be possible to run smoothly this plugin using all the checks without inconvenience.

Go back to the Best Practices article.