Open lostintangent opened 8 years ago
There are several perf issues that we know about once you start getting into scenarios that have large amounts of log statement. We believe we know what needs to be done to improve this greatly, just a matter of scheduling the work.
Update: I noticed that this perf issue seems to be related to requests with lots of logs, so the virtualization work for the list that Mike mentioned in another bug would likely improve it.
Repro steps:
/create
routeExpected: For the expand/collapse action to "feel" fluid/instant-ish Actual: It seems to take about a second to perform this action, which definitely feels a little slow, and begins to be a bit painful when navigating a deep object.