IGNITE-12555 .NET: Fix SerializableSerializer performance #7285
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.
Use cached binary metadata when possible: route all metadata through
Marshaller
, handle caching there.Before the fix, we had a
IBinaryProcessor.GetBinaryType
call for every deserialized object that implementsISerializable
, which caused huge performance drop, especially for thin client where every call is a network operation. The most commonISerializable
type isDateTime
.Perf measurements:
GetAllEmployeesBenchmark
+56%ThinClientGetAllEmployeesBenchmark
+2000%GetBenchmark
+30%ThinClientGetBenchmark
+20%