You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Context
BinaryFormater serialization of on-disk RAR cache is slow and unsecure.
Related issue: #6057
### Changes Made
Serialization changed to use custom binary format by using existing `ITranslatable`
### Testing
Unit testing
Manual testing
- Roslyn repo rebuild + incremental build
Issue Description
BinaryFormater serialization of on-disk RAR cache is slow.
Optimizing deserialization time will likely be synergic with RAR pre-caching goals.
Steps to Reproduce
Incremental rebuild or Roslyn repo.
Data
For Roslyn incremental build reading and parsing the RAR cache took almost 40% of RAR wall-clock time.
Analysis
When looking for optimal solution benchmark was create to measure serialization and deserialization of real project RAR cached data.
After evaluating pros and cons decision has been made to implement serialization as custom binary format, hand written code.
During this decision following was considered:
Versions & Configurations
Measured at latest production dotnet 5.0.102 SDK.
The text was updated successfully, but these errors were encountered: