Deprecated Catapult GitHub. Please instead use http://crbug.com "Speed>Benchmarks" component for bugs and https://chromium.googlesource.com/catapult for downloading and editing source code..
Thread pools are pretty common and are core foundational concepts in programming on iOS & OSX. However, the tracing display doesn't get it right. The core grouping concept is the thread ID which is meaningless for thread pools as any given thread in a thread pool can process from several conceptual queues. It would be nice to be able to have some convention that let the trace viewer display thread pools more elegantly (e.g. grouped by the task name regardless of which thread the activity occured on, perhaps with a triangle expansion to show which specific thread each job executed on).
Thread pools are pretty common and are core foundational concepts in programming on iOS & OSX. However, the tracing display doesn't get it right. The core grouping concept is the thread ID which is meaningless for thread pools as any given thread in a thread pool can process from several conceptual queues. It would be nice to be able to have some convention that let the trace viewer display thread pools more elegantly (e.g. grouped by the task name regardless of which thread the activity occured on, perhaps with a triangle expansion to show which specific thread each job executed on).