According to reports by Daniel Beck, accessing the activity page in some cases (eg for blueocean job on dogfood) pints the CPU to 100% and doesn't render.
Switch to a responsive table component
Tom FENNELLY was able to reproduce with the URLs I provided.
~140 vs. ~360 entries.
Thanks Daniel - that is interesting, there may be some ineffeciency going on that tips it over the edge at that number, or something data related.
Tom FENNELLY did you get to try this out yourself at all?
Tom FENNELLY switching to a more proven table component might help this? Facebook use this one in production, it has features I want for our table component we will need soon and I'd like us to consider it. See JENKINS-37233
Looks like the react dev tools are a big part of the problem. I think we can remove that during the build process. We should do that and see what difference it makes.
BTW, I also notice on the console on Firefox (not on others) that there is a warning ...
TypeError: mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create
This is coming from babel generated code in react-redux.