Open A-Maugli opened 2 days ago
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 https://github.com/AustP/austs-one-click-node/issues/39#issuecomment-2489412634, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN5I55REHB5H2QBUGRNFACL2BTRFRAVCNFSM6AAAAABSDFC42CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZGQYTENRTGQ . You are receiving this because you authored the thread.Message ID: @.***>
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?