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

Release/performance 2.8 #656

Merged
merged 11 commits into from
Nov 29, 2024
Merged

Release/performance 2.8 #656

merged 11 commits into from
Nov 29, 2024

Conversation

JamesPiechota
Copy link
Collaborator

No description provided.

vird and others added 11 commits November 13, 2024 12:10
Co-authored-by: Lev Berman <ldmberman@proton.me>
Initialize poa caches for initial block cache blocks
This commit adds the packing difficulty in `v2_index_data_size_by_packing`
metric.

see: ArweaveTeam/arweave-dev#568
This gives a truer estimate of the miner's expected read performance
This fixes an issue where read performance was severely degradeed
when multiple storage modules were stored on a single disk. This
was particularly bad for SATA, although was noticeable on SAS disks
as well.
Only current (active) peers should be able to receive the
chunks, others will generate unnecessary timeouts. In fact
using the active peers from the last 24 hours can also be
a great solution if we assume a peer seen during the last
24 hours will probably be come back quick.

When chunks are propagated across the network, the to be
acknowledged are the trusted peer. On the previous version,
the trusted peer where put at the end of the list.

Cleaned up ar_tx_emitter_sup, converting old tuple to map.

Refacto and added comments and documentation.

see: ArweaveTeam/arweave-dev#720
When a server has the full transaction locally, and uses
spinning disk, the amount of requests from other nodes is
too high, and leads to a bottleneck on rocksdb database.

This commit adds a semaphore to control the amount of
requests on `ar_http_iface_middleware:handle_get_tx/3` function,
to avoid a node to be overflooded by requests.
For the first ~2 months after the 2.8 HF activation nodes
may have less than the required 3 months of reward history.
This is okay.
@JamesPiechota JamesPiechota merged commit 6ad4bc8 into master Nov 29, 2024
59 of 67 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants