Closed effectfully closed 4 days ago
/benchmark validation
/benchmark validation
/benchmark validation
Click here to check the status of your benchmark.
Comparing benchmark results of 'validation' on '5eb80f3fe3' (base) and '07263b5a36' (PR)
5eb80f3 | 07263b5 | Change | |
---|---|---|---|
TOTAL | 44.50 ms | 44.38 ms | -0.3% |
Click here to check the status of your benchmark.
Comparing benchmark results of 'validation' on '5eb80f3fe3' (base) and '07263b5a36' (PR)
5eb80f3 | 07263b5 | Change | |
---|---|---|---|
TOTAL | 44.60 ms | 44.42 ms | -0.4% |
Click here to check the status of your benchmark.
Comparing benchmark results of 'validation' on '5eb80f3fe3' (base) and '07263b5a36' (PR)
5eb80f3 | 07263b5 | Change | |
---|---|---|---|
TOTAL | 44.55 ms | 44.14 ms | -0.9% |
/benchmark validation
Click here to check the status of your benchmark.
Comparing benchmark results of 'validation' on '5eb80f3fe' (base) and '07263b5a3' (PR)
5eb80f3 | 07263b5 | Change | |
---|---|---|---|
TOTAL | 44.36 ms | 44.44 ms | +0.2% |
Meh, not worth working on it I believe.
unsafeFreezePrimArray
seems entirely unnecessary there. Let's check if this is the case and if we can save any work by removing it. Quite possible it's the opposite and we'll get a slowdown here.