-
Notifications
You must be signed in to change notification settings - Fork 12
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
A1CN very slow #39
Comments
No, that doesn't seem right. As to why that happened, I cannot say. Things you could try are restarting the app or reinstalling the app. |
The issue may be connected with high GPU 3D usage, typically around 30
percent. My PC has an NVidia GeForce GTX 1650.
When I started the A1CN, it began to synchronize again, although yesterday
the mainnet was already synced.
…On Wed, Nov 20, 2024 at 8:45 PM Aust ***@***.***> wrote:
No, that doesn't seem right. As to why that happened, I cannot say. Things
you could try are restarting the app or reinstalling the app.
—
Reply to this email directly, view it on GitHub
<#39 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN5I55REHB5H2QBUGRNFACL2BTRFRAVCNFSM6AAAAABSDFC42CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGQYTENRTGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I have reinstalled the A1CN app, and spun up Algorand mainnet. But this time I kept the app in minimised state, and it run a little faster, under 12000 sec. What else do you recommend to try? |
Sometimes there's a cache file that gets messed up. Turning off the app and then deleting the folder and then starting the app will cause a long resync but then it is good after that. The folder to delete is based on your OS: Windows: "C:\Users\username\AppData\Roaming\Austs One-Click Node\data\algorand.mainnet" |
On a PC with a 8-core CPU, 16 GB, under WSL2 the algod sync takes about 5500 sec.
Under Win10 A1CN V1.5.0 is now running for 14086 sec, and still not ready. Is it normal?
Why is the Win10 version so slow, compared to WSL2 algod?
The text was updated successfully, but these errors were encountered: