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
Report: that worked until GCC started compiling. Turns out no, the scheduler cannot handle it. VM was already isolated to one NUMA node, so now I'm sending emerge off to the other one (CPUs only, let's let it use all free RAM).
Yup, that worked fine. A few dropped frames here and there while compiles were pegging one side, but nothing terrible. Beat Saber plays fine.
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).
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
