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.

Sign up for GitHub

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

Jump to bottom

Investigate outcome of stress test #1358

Open
muXxer opened this issue Mar 23, 2022 · 1 comment
Open

Investigate outcome of stress test #1358

muXxer opened this issue Mar 23, 2022 · 1 comment
Assignees
@alexsporn @muXxer
Milestone
HORNET-v2.0.0

Comments

@muXxer
Copy link
Collaborator

muXxer commented Mar 23, 2022 •
edited by luca-moser
Loading

Checkout logs/captures and find the bottlenecks causing the highest resource usage at the node's breakpoint.
@muXxer muXxer added this to the 2.0.0 - Stardust Devnet milestone Mar 23, 2022
@alexsporn alexsporn modified the milestones: Stardust Testnet, Shimmer Launch Apr 13, 2022
@luca-moser luca-moser modified the milestones: v2.0.0-rc, v2.0.0 Jun 7, 2022
@muXxer muXxer added the priority-rc Issues which are needed to ship the RC version of the software. Aka, ready for Shimmer. label Jun 7, 2022
@luca-moser luca-moser removed the priority-rc Issues which are needed to ship the RC version of the software. Aka, ready for Shimmer. label Jun 8, 2022
@luca-moser luca-moser changed the title Stress tests Investigate outcome of stress test Aug 16, 2022
@muXxer
Copy link
Collaborator Author

muXxer commented Aug 22, 2022 •
edited
Loading

First investigations:

hornet:

  • keeping the latest cone completely in RAM would reduce parents and childrens walk workload by a lot
  • signature checks are quite heavy and currently single threaded

inx-coordinator:

  • almost no CPU load even at 1000 BPS

hornet node of inx-coordinator:

  • high CPU load because of garbage collection and whiteflag
  • its double the CPU load of other nodes (whiteflag is done twice per milestone)

inx-dashboard:

  • creates unnecessary CPU load if no client is connected to fill the visualizer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexsporn alexsporn

@muXxer muXxer

Labels
None yet
Projects
None yet
Milestone
HORNET-v2.0.0
Development

No branches or pull requests
3 participants
@luca-moser @alexsporn @muXxer