4 ms·
It was in a typeahead search application built on 20GB of names. These names have common first names and last names which were stored as different strings. With
by karthikkolli 12y ago
It was in a typeahead search application built on 20GB of names. These names have common first names and last names which were stored as different strings. With deduplication, string memory was reduced to 20%
Will benchmark that application with +UseStringDeduplication
- chrisseaton 12y agoSo what was the downside of deduplication? Why did you want to avoid it?
- karthikkolli 12y agoSorry deduplication was a typo. Corrected
- chrisseaton 12y agoAh right. The reason they're doing it in the GC rather than in the mutator threads is that it only has an impact on strings long lived enough to be evacuated. Short lived strings don't get deduplicated, and probably don't need to be. Without the GC I don't know how you'd automatically determine that it was a good idea to deduplicate.