Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #2058] Grids are still fetching all rows under certain conditions #568

Closed
icinga-migration opened this issue Nov 10, 2011 · 2 comments
Labels

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/2058

Created by tgelf on 2011-11-10 12:27:12 +00:00

Assignee: mhein
Status: Resolved (closed on 2011-11-16 16:11:20 +00:00)
Target Version: (none)
Last Update: 2011-11-16 16:11:20 +00:00 (in Redmine)


There have been similar issues before, however it may still happen that the browser is blown up by thousands of rows (several MB) provided as a JSON response, going to be paginated in the EXT grid.

User experience: 1.5 is slow, kills the browser. To reproduce this: open Service Status, add a Filter, choose a hostgroup with a total of at least more than 25 services, have a look at JSON resultRows there will be all of them, pagination is done in the browser.

The attached patch is a quick attempt to fix this in the view, I'm not sure whether that's the right place. I don't care WHERE you're going to fix this, but please do so ;-)

cheers,
Thomas

Attachments

Changesets

2011-11-16 15:41:09 +00:00 by mhein 42223ed

* Applied patch to fix initial pagination (THANKS TO Mr. Gelf) fixes #2058
@icinga-migration
Copy link
Author

Updated by mhein on 2011-11-10 15:42:50 +00:00

  • Target Version deleted 1.6

@icinga-migration
Copy link
Author

Updated by mhein on 2011-11-16 16:11:20 +00:00

  • Status changed from New to Resolved
  • Done % changed from 0 to 100

Applied in changeset 42223ed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant