-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2023-10-17] Speedup getOrderedReportIDs by comparing strings instead of Dates objects #28001
Comments
Triggered auto assignment to @miljakljajic ( |
Bug0 Triage Checklist (Main S/O)
|
This issue has not been updated in over 15 days. @miljakljajic, @allroundexperts, @mountiny eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
This is ready for payment and its $500 to @allroundexperts for internal review and testing |
Payment summary: $500 to @allroundexperts for internal review and testing @allroundexperts please request payment in newDot! |
$500 payment approved for @allroundexperts based on summary above. |
Problem
For some reason creating Date object is super slow on Hermes. So @janicduplessis came up with the idea to compare strings instead. It will generate a different output but the error is only under 1s. The reason for that is that milliseconds representation can has different length.
Using this solution:
the method now runs under 1s instead of 14s (when starting heavy accounts
The text was updated successfully, but these errors were encountered: