Good to know. It’s probably worth emphasizing that anyone suffering this issue should still take a look at their code, and especially the way they increment translational/vector related data every frame, as I suspect a great many of the issues surrounding this are related to that.
That, and just generally keeping an eye on each major process you finish coding to get a feel for its performance. I always run some tests on each major code path I connect to Update() or Draw() to get a feel for how much CPU crunching is going on. Processes I wouldn’t expect to be costly can be, and things I imagined would need a lot of cycles ended up being trivial.
I suppose a good long-term solution to this would be to implement some debug performance tracking classes which you can insert here and there in your major code paths to keep track of all that.