CPDAVD High server load on login

[Mike_bd]

Hi,

Ever since updating to version 96, I've noticed that I'm getting high server load on logging into web disk on my PC. I only have to log in the once (and it's only me who has access to the server) and it causes this for the first 15 to 20 minutes or so.

The server usually averages around 0.20 load throughout the day. Anyone else have this issue?

I've attached a screenshot. Notice how there are 20 instances of "cpdavd - authenticated as" and the server loads shot up to 18.15 6.68 and 2.50.

 

[cPRex]

Hey there! I don't currently have any other reports of similar cases. Do you know if you have users that take advantage of the cpdavd services? That process would control the WebDisk service on the machine, and it would be odd to have so many processes running at once. On a test server with no connection, I only see the output like process 29216 in your list:

# ps aux | grep cpdav
root      2761  0.0  0.3 183652  5928 ?        Ss   May30   0:06 cpdavd - accepting connections on: 2079, 2080, 2090, 2091, 2077, 2078 (dormant)

You could always disable this service briefly during the period of high load in WHM >> Service Manager to see if the load goes down with that service off.

 

[Mike_bd]

Hey!

Thanks for the reply. I'm the only person with access to this server and web disk as it was set up as a test/dev server. I've just noticed though that this happens when i open Visual Studio Code (which is hooked up to a couple of folders on the server as workspaces)… and I usually open this as soon as i log in.

Just tried a few times and it looks like for each tab I have open in Visual Studio Code when i load up, it produces one of those "cpdavd - authenticated as". Seemed to do this after upgrading to v96 but then again, VSC may have updated around the same time.

I'll keep an eye on it. But that's a lot of resource being taken for a bunch of small js files being read.

 

[cPRex]

That makes sense. It's not so much the files that you're working with, but the back-end processes that are put into place so Visual Studio can connect and manage files.