Hi Alumio,
We’ve noticed the UI has become significantly slower in the last +/- 6 months. I think this isn’t ‘just’ due to the inspection tool, but I do believe it’s probably the most significant driver.
Especially when working with large datasets (i.e. a product with children, containing +/- 70.000 JSON lines and is multiple levels deep), it slows down to a crawl. I think this is mostly due to the inspection tool, because when ‘just’ loading the transformer (including the large test-data) it’s reasonably fast, but when you click ‘run test’ just once, it becomes very slow.
I remember this behaviour from the previous incarnation of the inspection tool as well (‘data points’ I think?), but there it was a conscious choice to actually enable the data point. If you didn’t need it, you could just keep it disabled so it stays quick.
I understand this is a very complicated issue, but slowing the UI down so much it becomes unusable is also not really an option. We’d like the ability to either completely shut down the inspection tool’s ‘capturing’ of through-put data, or bring back the option to explicitly set which points should capture that data.