Skip to content
This repository has been archived by the owner on Aug 27, 2023. It is now read-only.

Commit

Permalink
First draft performance troubleshooting page (hyperledger#1335)
Browse files Browse the repository at this point in the history
* First draft performance troubleshooting page.

Signed-off-by: Matt Nelson <[email protected]>

* tweaks and linter

Signed-off-by: Matt Nelson <[email protected]>

* edit PR content

Signed-off-by: Alexandra Tran <[email protected]>

---------

Signed-off-by: Matt Nelson <[email protected]>
Signed-off-by: Alexandra Tran <[email protected]>
Co-authored-by: Alexandra Tran <[email protected]>
  • Loading branch information
2 people authored and joshuafernandes committed Jun 21, 2023
1 parent c1b8981 commit fbc9169
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion docs/public-networks/how-to/troubleshoot/performance.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,12 @@
---
description: Troubleshoot poor performance and resource constraints.
<<<<<<< HEAD
sidebar_label: Troubleshoot performance
sidebar_position: 3
tags:
- public networks
=======
>>>>>>> 64d8a8a (First draft performance troubleshooting page. (#1335))
---

# Troubleshoot poor performance and resource constraints
Expand Down Expand Up @@ -42,4 +45,4 @@ try the following suggestions:
You can run your consensus client on the same machine, but this adds overhead on Besu, and vice
versa (on CPU cache misses, CPU scheduler latency, IO, etc.).

You should continue to monitor your node after following these suggestions.
You should continue to monitor your node after following these suggestions.

0 comments on commit fbc9169

Please sign in to comment.