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] PostgreSQL in service node: Further optimisations #84

Closed
8 tasks done
fryorcraken opened this issue Sep 7, 2023 · 0 comments
Closed
8 tasks done

[Epic] PostgreSQL in service node: Further optimisations #84

fryorcraken opened this issue Sep 7, 2023 · 0 comments
Labels
E:PostgreSQL See https://github.com/waku-org/pm/issues/84 for details Epic Tracks a sub-team Epic.

Comments

@fryorcraken
Copy link
Contributor

fryorcraken commented Sep 7, 2023

Epic label: E:PostgreSQL

Summary

Further optimisation of PosgreSQL usage for Waku archive in nwaku.
Specifically to cover the case of Status Communities and 10k users in a given Community/shard/store.

Acceptance Criteria

  • Various optimization/performance fix have been implementing.
  • Performance analysis done and follow-up items are implemented.

Note that while go-waku also implements PostgresSQL, the focus is on nwaku as a service node.
Providing store service from Status Desktop app is not part of the scope of this epic.
This will be possible/interesting once #57 is done.

Tasks

RAID (Risks, Assumptions, Issues and Dependencies)

@fryorcraken fryorcraken added the Epic Tracks a sub-team Epic. label Sep 7, 2023
@fryorcraken fryorcraken added the E:PostgreSQL See https://github.com/waku-org/pm/issues/84 for details label Sep 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E:PostgreSQL See https://github.com/waku-org/pm/issues/84 for details Epic Tracks a sub-team Epic.
Projects
Status: Done
Development

No branches or pull requests

2 participants