See D18006 for discussion, this view library potentially makes a lot of DB calls with the markup engine, it should be batched (since I'm probably going to drop in replace the History view in Diffusion with it.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | chad | T12824 Redesign Diffusion | ||
| Wontfix | epriestley | T12749 Performance test and tune DiffusionHistoryListView |
Event Timeline
Comment Actions
I think using a Pool (like HandlePool) is not too much more work (at least, if I'm implementing it) than AJAX it and will be useful in more cases. I believe we need the Pool implementation regardless, sooner or later.
If you're comfortable doing an AJAX implementation and want to hook that up, I think that's fine to ship and then I can replace it with a Pool implementation when I have a chance. If this is ending up on my plate either way, I don't think there's a big time savings from doing AJAX.
(There's also maybe some interaction with T9713 here, although we could retrofit that easily enough later.)
Comment Actions
Yeah I just didn't want to add the (...) view to DiffusionHistory if it's going to slow those pages down. I'd just leave the feature out.
Comment Actions
There's no specific performance/scale issue here, so waiting until one arises or this pops up on a profile.