-
Notifications
You must be signed in to change notification settings - Fork 1
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
Time performance #1
Comments
Sure thing ;-) UUID generation benchmark : This is pure generation benchmark, so it's not entirely honest since all implementations do not do exactly the same thing upon generation. For example Webpatser/Uuid does pre-compute the string representation after having generated the binary form. SoUuid lazy generates string and Hex forms, so this work is done after, but, if you consider that the whole point of doing this is to optimize inserts, hence to use the binary form, then, SoUuid has no overhead to provide with the binary form as it is the root form. No need to say that if the differences are pretty significant, we are still talking about winning at best one sec per million UUIDs, so it's clear that the actual optimization is not here, but in the massive insert, see benchmarks here https://www.percona.com/blog/2014/12/19/store-uuid-optimized-way/
Will commit the bench, it may not be working yet on PHP below 7 as I don't have any <7.0 64 bit version ATM thus cannot test. |
Hey @fab2s, awesome work you just done here !
Can you share time performance benchmarks for generate SoUuid's vs Uuid's ?
The text was updated successfully, but these errors were encountered: