Open dstokes opened 10 years ago
it's building indexes and stuff, but leveldb does this for some reason. but this will go away eventually, if it's bothering you restart the process - all the index building processes will recover.
multiple restarts yield the same results, but probably just need to wait for the indexes to finish building. thx :)
I'm gonna leave this issue open, because hopefully this is fixable, but it might be a leveldown fix or something like that.
I have that issue too, also during npmd --sync
...
CPU was at 108% and I could not move my mouse cursor anymore.
oh! that is bad! I'm gonna rewrite this all soon, hopefully I'll be able to address this problem.
when restarting the sync command with
npmd --sync
, cpu load hovers over 100% even though it reports being fully synced. is this expected?machine: MacBook running OSX 10.9