This is the first report of this I have heard - I don't think we have made any changes to that visualizer in several years, so it is possible that a dependency has changed/regressed, causing an issue. Can you confirm for me that this is using the same data in both environments? Are you comfortable sharing these data with me? If so, feel free to send me a link here or in a DM, I will attempt to diagnose there.
Thanks for sharing @bayegy, and yes, I can confirm the slowdown. I totally forgot about this, but we refactored part of that viz to allow for more transparent code-reuse, I suspect the slowdown is related to that, and I'm not sure if there is much for us to do about it at this point. As far as resource consumption, this visualizer has no concept of parallelism or concurrency, so you shouldn't see any change in the number of CPUs working.