Use AtomicString for PerformanceEntry::name
This CL changes the name of a PerformanceEntry to become a name. It should be noted that in general performance entries can be accessed from main or worker threads, so some care is needed. An exception to this is paint and longtask entries, and appropriate DCHECKs were added for those cases. Assessment of this change: Speed: AtomicString comparisons are faster but this CL increased the number of conversions between string types. So overall unclear, but likely insignificant speed changes. Memory: PerformanceEntry names are now shared so the memory usage should be improved by this change. Code complexity: increased (AtomicStrings are IMO harder to reason about than slightly simpler Strings). Bug: 852050 Change-Id: Iaee67c6bcd6123851a0f6657d12fb6b2c61cb5fc Reviewed-on: https://chromium-review.googlesource.com/1153608Reviewed-by:Jeremy Roman <jbroman@chromium.org> Reviewed-by:
Timothy Dresser <tdresser@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#579609}
Showing
Please register or sign in to comment