Why is ProVide using a lot of CPU, and how can I reduce it?

In most cases this is temporary. High CPU use in ProVide almost always shows up when HTTPS is enabled with indexing turned on and the server is working through a large number of files and folders for the first time. That initial indexing pass is expected, and CPU use returns to normal once it finishes.

If you want to cap how much of the system ProVide uses, you can tune a few values in the settings.ini file:

[Maximum SendBufferSize] 8388608
[Maximum RecvBufferSize] 1048576
[Disk Write Buffer Enabled] True
[Disk Write Buffer Size] 65536
[Max background threads for cache updates] 16

Stop the ProVide service before you edit settings.ini. If the service is still running when you save, it can overwrite your changes as it shuts down, so they will not take effect.

If a small resource footprint matters for your deployment, ProVide is built to run lean on both Windows and Linux, whether you host it on-premises or in the cloud.