Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Correctly account for cpu usage by background threads #4074
Can we do something to reduce the boiler plate? It makes it hard to follow if everything starts with
self.hs.get_reactor(), self.hs.get_reactor().getThreadPool(). Could we maybe make
defer_to_threadpool take a
hs object? Or even just the reactor and call
getThreadPool() on it inside the function?
Otherwise looks good.