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

Investigate db slowdown #32

Open
chenglou opened this issue Sep 16, 2016 · 4 comments
Open

Investigate db slowdown #32

chenglou opened this issue Sep 16, 2016 · 4 comments

Comments

@chenglou
Copy link
Collaborator

screenshot 2016-09-16 01 42 36

The db takes a couple of hundred of ms running, for some reason. It's erratic too (sometimes only takes a few ms).

@vramana

@vramana
Copy link
Contributor

vramana commented Sep 16, 2016

I don't know how to approach this even. On my machine, I saw it to be around 350ms.

@chenglou
Copy link
Collaborator Author

Still means something's wrong. It should be around 10ms

@jordwalke
Copy link
Collaborator

I definitely noticed a significant slowdown when using rebel (compared to the previous version I was using). I'll let you know if I think of other reasons why, but did we make sure to blacklist searching of node_modules that aren't actually related? That could take a huge amount of time with a typical npm install.

@jordwalke
Copy link
Collaborator

jordwalke commented Sep 29, 2016

Not sure if this is relevant, but I see a bunch of these warnings, not sure if it is related to the slowdown:

findlib: [WARNING] Package bytes has multiple definitions in

/Users/jwalke/Desktop/MyApp/node_modules/ocamlfind-actual/_build/ocamlfind/lib/bytes/META,
/Users/jwalke/Desktop/MyApp/node_modules/ocamlfind/_build/ocamlfind/lib/bytes/META

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