Open joncrlsn opened 4 years ago
KBFS is written in Go, which is notorious for not releasing virtual memory (but that doesn't actually matter usually to your system). The important thing to look at is the resident memory. If it's more than 1.5-2 GB or so, that could indicate a problem.
Thank you, strib! Java is not much better with releasing virtual memory. I love Go, though.
On a newly restarted Mac, Activity Monitor tells me it is using 150-200M, however htop tells me it is using 436M resident (and 4G virtual). I'm not sure if I should believe htop or Activity Monitor. They are probably measuring 2 separate things.
The next time Activity Monitor reports high usage I'll check htop to compare. Thank you again.
MacBook Pro with 16GB RAM. This may not be a serious problem given that I've been copying groups of files into KBFS. The largest was a 700MB group of files, and I didn't let KBFS relax before doing the next group of files. As things got slow keybase noticed and asked me to send logs. I then checked Mac Activity Monitor. kbfs appears to have exploded in memory usage (some of it must actually be virtual memory since I only have 16GB of RAM on this machine.)
my log id: 15d717316c201456bc46e71c
There is nothing I need right now. I'm just letting keybase catch up with all the encryption it needs to do.