Um, sounds like some of the HE staff believe in bigfoot:
Yes, the engineers (myself included) are working on it. There is a handful of improvements still being tested internally. If I had to guess, the one most likely to affect your hub is improved event history management. We saw folks who updated to to 2.2.3 reporting much better response times after nightly cleanup job has run. So why not do a cleanup when hub starts and avoid sluggish response until overnight job? Hindsight 20/20... Hopefully this fix will deal with the slow hub issue. We'll kee…
We have a new beta version that trims states and events on startup, among other things. One of the common slowdown causes of general slowdown is a large number of either stored in the database, so there's a good chance this new beta will help once it becomes available. Right now, it is at a point of getting user feedback, so it shouldn't be too long.
Maybe "events" in this context means something different from "events that the user chooses to log", and maybe there are "event history" entries that are not controlled by user level logging settings.
Perhaps the terminology could be clarified to distinguish those classes and put an end to the Nessie sightings.