[threadpool] Experiment with thread reclaim time.
This CL creates a base::Feature to change the thread reclaim time from
30 seconds to 5 minutes (75th percentile of time it takes to recreate
a thread after it has been detached). The goal is to scientifically
determine what value provides the best speed / memory trade-offs.
Previous experiments explored detach times of 300 ms, 30 seconds and
8 hours, and concluded that 30 seconds was the best value. A detach
time of 5 minutes has never been tried.
Bug: 945681
Change-Id: I9cde77169347491d136b21194a0506d360ca37e1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1678438
Auto-Submit: François Doray <[email protected]>
Commit-Queue: Gabriel Charette <[email protected]>
Reviewed-by: Gabriel Charette <[email protected]>
Cr-Commit-Position: refs/heads/master@{#672901}
diff --git a/base/task/task_features.h b/base/task/task_features.h
index ac1ae97..be1f70a5 100644
--- a/base/task/task_features.h
+++ b/base/task/task_features.h
@@ -37,6 +37,10 @@
extern const BASE_EXPORT Feature kUseNativeThreadPool;
#endif
+// Whether threads in the ThreadPool should be reclaimed after being idle for 5
+// minutes, instead of 30 seconds.
+extern const BASE_EXPORT Feature kUseFiveMinutesThreadReclaimTime;
+
} // namespace base
#endif // BASE_TASK_TASK_FEATURES_H_
