global io executor
Summary: This is something we've talked about for a while. It's also an alternative to the mechanism in D1714645. If we like it, I'll do something similar for a global cpu executor. That functionality should probably just be baked into Executor itself instead of a separate subclass, which is why the IOExecutor stuff is in Executor.h/.cpp, because it'll be pretty similar. The main exception is that for getCPUExecutor() you could return a default global InlineExecutor instead of exploding as in getIOExecutor() Test Plan: wangle unit, will start plumbing this into the services in #5003045 if we like it Reviewed By: davejwatson@fb.com Subscribers: hannesr, trunkagent, fugalh, alandau, mshneer, folly-diffs@, bmatheny FB internal diff: D1727894 Tasks: 5002442 Signature: t1:1727894:1418344077:9e54088a6acb3f78e53011a32fd1dfe8b3214c1d
Showing
Please register or sign in to comment