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
Following #20 where I've been able to remove a bottle neck and increase the replay speed, I believe the next big step will be to enable multiple CPU cores usage for the heavy-weight operations that avalon does. So basically I want to do it for the signatures verification, which represent the ultra-majority of the CPU cycles used, and should improve the replay speed a lot for people with 3 cores or more. 2 cores won't change much because mongodb's process is usually already clusterized and will make use of the 2nd core already.
This would greatly improve the replay speed, especially for people using scalable cloud solutions, where it would then be possible to increase your CPU to replay faster, and turning it down once synced.
The text was updated successfully, but these errors were encountered:
Following #20 where I've been able to remove a bottle neck and increase the replay speed, I believe the next big step will be to enable multiple CPU cores usage for the heavy-weight operations that avalon does. So basically I want to do it for the signatures verification, which represent the ultra-majority of the CPU cycles used, and should improve the replay speed a lot for people with 3 cores or more. 2 cores won't change much because mongodb's process is usually already clusterized and will make use of the 2nd core already.
This would greatly improve the replay speed, especially for people using scalable cloud solutions, where it would then be possible to increase your CPU to replay faster, and turning it down once synced.
The text was updated successfully, but these errors were encountered: