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

[Epic] Speed optimizations #1521

Open
1 of 4 tasks
weboko opened this issue Sep 1, 2023 · 1 comment
Open
1 of 4 tasks

[Epic] Speed optimizations #1521

weboko opened this issue Sep 1, 2023 · 1 comment
Assignees
Labels
epic Tracks a yearly team epic (only for waku-org/pm repo)

Comments

@weboko
Copy link
Collaborator

weboko commented Sep 1, 2023

Planned start date:
Due date:

Summary

Tracks the work done on js-waku to improve speed, latency, and other critical parameters to the fluency of js-waku.
Items may come from:

  • core contributor's research
  • feedback from consumers

Acceptance Criteria

This is a yearly milestone as such report and feedback may happen as long as the library is used.

Bug reports should only be tracked here if not related to a 2023 development.

Tasks

RAID (Risks, Assumptions, Issues and Dependencies)

  • This cannot happen if there is no usage of the API
  • Some issues may come from contributors, consumers, partner teams
@weboko weboko self-assigned this Sep 1, 2023
@weboko weboko added the epic Tracks a yearly team epic (only for waku-org/pm repo) label Sep 1, 2023
@fryorcraken
Copy link
Collaborator

Investigate re-usability of streams (comment);

We confirmed that libp2p's best practice is to *not re-use a stream for req-res protocols.

The first item is already tracked in #1465 so not sure to see a need to double track.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Tracks a yearly team epic (only for waku-org/pm repo)
Projects
Status: To Do
Development

No branches or pull requests

2 participants