Hello.
I tried 1.110 on my nodes .
Budger cashe is on.
interesting that on other server there no such problem, but there i didnt restarted server after update, and other server has 12700k cpu and 64GB RAM
On this server I see intence C drive usage, so DBs are in play and may be page files
So the dbs are on HDD instead of SSD right?
Do not joke that, only on SSD, it is even NVME
Oh okay, then it seems v1.110 is about to test my new SSD Raid10 
I think it may be batch deletes, also budger filewalker use full filewalker to scan pieses.
Does the badger db just go into the SSD as set by
storage2.database-dir:
or did you have to move them manually somehow?
I can’t wait to see it running on my NAS with Arm 4 cores and 1 GB of RAM and without SSD 
budger cache is on HDD, cant move it on windows. I asked to make it movable as DBs but, it takes time and effort.
I think that’s why OP believes they’re seeing higher load than before. Lazy filewalker was kind to the HDD… non-lazy-badgerdb filewalker rules with an iron fist 
Ooof!
Sounds like a step in the wrong direction, doesn’t it? 
1.109 will give you the same picture if you start/restart several nodes with turned on badger cache and enabled scan pieces on startup at the same time. In my case high CPU usage lasts only 2-3 minutes (probably, while filewalkers are working). Filestatcache is on SSD.
i used to have a xeon 2680v4! It was nice.
if you need a few more cores you can get a 2697 or 2699 really cheap now.
Looks like I found the problem, it was me.
I tried add RAM memory before, it was failed, and i Inserted old memory back, but wrong slots, it worked but very slow.
