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

Slow build process – receive rate stuck at 0 most of the time #6073

Open
CryptoCanada opened this issue Jan 13, 2025 · 1 comment
Open
Labels

Comments

@CryptoCanada
Copy link

Hi, I'm currently in the process of building a Cardano node on an Ubuntu virtual machine following the official Cardano node installation instructions. However, I’ve noticed that my receive rate is at 0 for most of the time, which is causing the build process to be extremely slow.

I’d like to apologize in advance for my ignorance—I’m completely new to this and have zero experience in setting up or running nodes. That said, I’m incredibly excited to learn and contribute to the decentralization of the Cardano network. If there’s anything I can check or configure to improve the receive rate and speed up the build, I’d be very grateful for your guidance!


Steps to Reproduce:

  1. Set up a fresh Ubuntu VM on VirtualBox.

  2. Follow the official Cardano node installation instructions.

  3. Observe that the receive rate remains 0 for most of the process, slowing down the build significantly.


Expected Behavior:

A consistent receive rate during the build process to ensure it completes faster.


Environment:

OS: Ubuntu 24.10 (desktop, amd64)

VM Specs:

CPU: 4 cores

RAM: 27014 MB

Disk: 250 GB (on a WD EasyStore 264D USB device)

Network: Extremely stable home Wi-Fi, capable of handling 14 devices without any lag or interference.

Cardano Node Version: 10.1.4 (#1f63dbf commit hash)


Additional Context:

I searched for related issues using 'receive rate' and found the following:

#5810: Query UTXOs by address performance varies vastly.

#3080: A small subset of nodes on Alonzo-purple do not respond to new connections.

#844: Flip some tracers for better performance.

However, none of these seem to address my specific problem. Any help would be greatly appreciated!

C4C
PXL_20250113_145234123

Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.

@github-actions github-actions bot added the Stale label Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant