Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
While writing an
ObjectId
-like class for another project (where I needed a time-based identifier, but didn't want to bring dependency on a wholeMongoDB.Bson
package just forObjectId
), I was curious about performance of my implementation compared to the reference one.My test was like serializing a million of identifiers (as strings), and then parsing them back. Here are my results:
ObjectId.ToString()
ObjectId.Parse()
So this probably looks like a valid reason to make a pull request and improve things a little :)
I'm not sure if it affects other cases where
ObjectId
is serialized, like performance of database responses' deserialization. But shouldn't hurt at least.