Project

General

Profile

Bug #5612

CPU cores getting maxed out by VCSServer on Repository Size request

Added by Renaud Lepage 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
08.04.2020
Due date:
% Done:

0%

Estimated time:
Sorting:
Commit Number:
Affected Version:

Description

Please note that this happens on a RhodeCode CE instance, running the latest RhodeCode code, but running on a Virtual Private Server machine with fairly "restricted" specs (one virtual CPU, 2gb RAM). Weak by any metrics.

Condition: Using a freshly imported SVN repository that's not indexed or anything

Hitting "Show Repository Size" starts some kind of "runaway process", or possibly a "go through each commit in historical order", from the RhodeCode "Main Service" (community-1) to the VCS Server. This makes the two VCSServer workers max out the one virtual CPU my VPS instance has for some reason - likely because VCSServer does some big processing on each commit to get the size, but I can't be sure.

Setting prio to Low because I'm not a paying client.

History

#1 Updated by Renaud Lepage 3 months ago

Additional detail I should have mentioned: the freshly imported SVN repository is known to be fairly big - gigantic, even.

Also available in: Atom PDF