You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
Note: I'm not 100% certain this is a defect, but I've observed it multiple times and wanted to report it.
OpenEthereum version: 3.0.1
Operating system: Windows
Installation: .exe
Fully synchronized: no
Network: ethereum (default)
Restarted: yes
Expected:
Memory/Cache performance and efficiency remains the same over time.
Actual:
Immediately after launching, Committed Memory and Working Memory are roughly equal in the Resource Monitor. After syncing for 24-48 hours, up to 2GB worth of Committed Memory remains unused even when observed for extended periods of time.
For reference, I'm using an about 12 GB cache and leaving my computer to run untouched for the period of time.
My theory is that over time, the allocated memory is becoming fragmented and unusable. Restarting fixes the problem and results in a small performance increase, but babysitting the process like this isn't ideal.
The text was updated successfully, but these errors were encountered:
Note: I'm not 100% certain this is a defect, but I've observed it multiple times and wanted to report it.
Expected:
Memory/Cache performance and efficiency remains the same over time.
Actual:
Immediately after launching, Committed Memory and Working Memory are roughly equal in the Resource Monitor. After syncing for 24-48 hours, up to 2GB worth of Committed Memory remains unused even when observed for extended periods of time.
For reference, I'm using an about 12 GB cache and leaving my computer to run untouched for the period of time.
My theory is that over time, the allocated memory is becoming fragmented and unusable. Restarting fixes the problem and results in a small performance increase, but babysitting the process like this isn't ideal.
The text was updated successfully, but these errors were encountered: