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
I was investigating proving performance on Apple M1 Max, and managed to double the proving speed by adjusting the number of threads/workers used in this config:
The associated issue has apparently been fixed in newer chromium (?) and/or nodejs. So i've upgraded to nodejs v21.4.0 and set the num workers to 7, which double my proving speed for 2^16 constraints from ~50s to ~24s.
I'm unsure of all implications this has for the bindings or o1js in general, but its a significant improvement from my sparse testing.
The text was updated successfully, but these errors were encountered:
I was investigating proving performance on Apple M1 Max, and managed to double the proving speed by adjusting the number of threads/workers used in this config:
o1js-bindings/js/node/node-backend.js
Line 142 in c5aa5f1
The associated issue has apparently been fixed in newer chromium (?) and/or nodejs. So i've upgraded to nodejs v21.4.0 and set the num workers to 7, which double my proving speed for 2^16 constraints from ~50s to ~24s.
I'm unsure of all implications this has for the bindings or o1js in general, but its a significant improvement from my sparse testing.
The text was updated successfully, but these errors were encountered: