Skip to content
This repository was archived by the owner on Feb 12, 2024. It is now read-only.
This repository was archived by the owner on Feb 12, 2024. It is now read-only.

High CPU when publishing files with js-ipfs #1190

Closed
@ido-ran

Description

@ido-ran
  • Version: js-ipfs/0.27.5
  • Platform: macOS High Sierra 10.13.2 (17C205)
  • Subsystem: Chrome Version 63.0.3239.132 (Official Build) (64-bit)

Type: Bug

Severity: Medium

Description:

I'm building a system in which js-ipfs node publish file and go-ipfs node get it, I'm using out-of-bound means to notify the content hash.
I've noticed that after a few seconds of fetching the file by go-ipfs the js-ipfs app in Chrome browser starts to have very high CPU usage between 50-100%.

Steps to reproduce the error:

Use webpack example app to publish a file (photo is easiest usually) and use gateway.ipfs.io it get it.

I've record a Chrome Performance session you can use to see the high CPU.

Metadata

Metadata

Assignees

Labels

P1High: Likely tackled by core team if no one steps upexp/wizardExtensive knowledge (implications, ramifications) requiredhelp wantedSeeking public contribution on this issuekind/bugA bug in existing code (including security flaws)kind/wontfix-migration-availablestatus/readyReady to be workedtopic/perfPerformance

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions