Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npmd --sync maxing cpu usage after full sync #51

Open
dstokes opened this issue Dec 6, 2013 · 5 comments
Open

npmd --sync maxing cpu usage after full sync #51

dstokes opened this issue Dec 6, 2013 · 5 comments

Comments

@dstokes
Copy link

dstokes commented Dec 6, 2013

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

@dominictarr
Copy link
Owner

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.

@dstokes
Copy link
Author

dstokes commented Dec 9, 2013

multiple restarts yield the same results, but probably just need to wait for the indexes to finish building. thx :)

@dstokes dstokes closed this as completed Dec 9, 2013
@dominictarr dominictarr reopened this Dec 10, 2013
@dominictarr
Copy link
Owner

I'm gonna leave this issue open, because hopefully this is fixable, but it might be a leveldown fix or something like that.

@binarykitchen
Copy link

I have that issue too, also during npmd --sync ...

CPU was at 108% and I could not move my mouse cursor anymore.

@dominictarr
Copy link
Owner

oh! that is bad!
I'm gonna rewrite this all soon, hopefully I'll be able to address this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants