-
Notifications
You must be signed in to change notification settings - Fork 324
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
High CPU usage of embedded node #450
Comments
Thank you for reporting this. Was it running against external or embedded node? |
Embedded node |
Embedded node uses js-ipfs, which is not as mature as go-ipfs. I was able to confirm problem under Chromium: after a few minutes with embedded node the CPU usage is indeed very high. Let's keep this issue open until upstream issues are resolved:
Workarounds for lowering CPU usageFor the time being I suggest using external node (go-ipfs) which requires smaller amount of resources.
Also related:
|
Why not just use the new WASM functionality of golang ? |
@gedw99 "just" is bit too optimistic :) We may investigate that route, but my intuition is that it won't be easy. There are low details (such as lack of raw socket API in web browser, storage) that require custom handling etc. Also, there is a huge benefit in having two independent implementations interop in the wild: it verifies if the spec is clear enough. It may be easier to optimize js-ipfs by introducing WASM (as a technology) in hot paths (eg. crypto), but that is a discussion for https://github.com/ipfs/js-ipfs. |
I installed the Chrome extension earlier today and found it to have high CPU usage. I don't think I was using any IPFS-compatible websites besides checking the ipfs.io blog.
macOS: 10.13.2
Chrome: 65.0.3325.181
IPFS Companion: 2.2.0
The text was updated successfully, but these errors were encountered: