Bug #5612
openCPU cores getting maxed out by VCSServer on Repository Size request
0%
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.
Updated by Renaud Lepage over 4 years ago
Additional detail I should have mentioned: the freshly imported SVN repository is known to be fairly big - gigantic, even.