You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Oh nice, it was just GCC competing on the other threads of the CCX that the VM was on?
Oh it was GCC competing on *all* the threads the VM was on. The VM was pinned, but GCC wasn't so it was trampling over everything (I was hoping the scheduler would prioritize the VM enough, but I guess it's not good enough to keep latencies low).
Ah that makes sense. I assume isolcpus isn’t appropriate here since the VM isn’t always running?
Correct.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
