Do logfile tailing for events (e.g. syslog) on a box creating many logfile events. Leave it tracking stuff for a while, then go to the events tab. This contains in my case 27k rows, tendency growing. In the longer run, this may result in memory issues (either the bowser growing too big or the server running oom while loading the items from the DB). We should introduce paging with e.g. 1k events per page.
The events list view should be paged with 50 items per page just like most of the other list views in the GUI. When I got to the events list view in hosted mode, I see the following in logs on the hosted mode console: [INFO] (RPCDataSource.java:131) 2011-12-13 15:16:11,439 [DEBUG] org.rhq.enterprise.gui.coregui.client.inventory.common.event.EventCompositeDatasource using [PageControl[firstRow=0, size=50, sort[timestamp DESC]]] for fetch request. [INFO] (TrackingRemoteServiceProxy.java:109) 2011-12-13 15:16:11,458 [DEBUG] RPC method invocation: EventGWTService_Proxy.findEventCompositesByCriteria This most likely means events are being paged correctly. Heiko, what led you to think the events were not being paged?
I guess you are right - what led me to this was the missing page buttons like we have/had in Struts/JSF land. Actually I've opened another BZ where the paging shows the red bar from time to time, so I think this one can be just closed.