Question Permanently Disable /usr/local/psa/admin/bin/statistics_collector

WebHostingAce

Silver Pleskian
Server operating system version
AlmaLinux 8.10 (Cerulean Leopard)
Plesk version and microupdate number
Plesk Obsidian 18.0.73 Update #3 Web Host Edition
Hi,

I know this topic has been discussed a few times before, but is there any way to completely disable the /usr/local/psa/admin/bin/statistics_collector process?

I’m running a very large website (around 600 GB) with high traffic, and I’ve noticed that this process runs daily from about 4 AM to 10 PM, consuming significant system resources.

Since I typically host only one customer per server, I don’t need disk usage or traffic statistics.

Is there a clean way to stop this process permanently without breaking anything in Plesk?

Thank you!
 
I assume that the statistics_collector is runs as part of the Plesk daily maintenance tasks. Which runs a whole bunch of specific sub tasks, listed here. Just a suggestion to consider, you could try to disable the daily maintenance cron and instead setup your own cron running each task separately but excluding the statistics related tasks. I am not sure however if the daily maintenance script runs any additional tasks that not listed. So in any case proceed with caution.
 
Sorry for the delayed reply!

Thank you very much, @Sebahat.hadzhi and @Kaspar .

I really wish there were an option to permanently disable /usr/local/psa/admin/bin/statistics_collector, as it’s a long-running and unnecessary process for us.

Hi, there. Unfortunately, there's no option to completely disable the process. It is part of the Plesk Daily Maintenance task and specific process cannot be isolated. The only alternative I can suggest to partially disable it by setting "Web statistics" for the domain in question to "None":

I’ve already done this, but the process is still running for hours.

For example:

1504559 be/4 root 353.24 M/s 0.00 B/s 0.00 % 56.40 % statistics_collector

As you can see, statistics_collector continues to consume a significant amount of I/O and CPU over a long period — and this is on an NVMe disk.
 
Back
Top