[
https://issues.apache.org/jira/browse/ARTEMIS-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443349#comment-17443349
]
Ha Anh Vu commented on ARTEMIS-3173:
------------------------------------
{quote} A little test that does the browse page view on messages that are paged
would be a good start point to be able to compare the responsiveness of getting
the 100th page when we start at 0 or 100*pageSize. \{quote}
Do you mean the current \{code} browse(int page, int pageSize, String filter)
\{code} starts at 0? Because when I look at the code \{code} long start =
(long) (page - 1) * pageSize \{code} it seems like it starts at 99*pageSize
(taking your example, getting the 100th page).
> Queue control browse message in paged mode should not start from the
> beginning each time
> ----------------------------------------------------------------------------------------
>
> Key: ARTEMIS-3173
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3173
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: JMX
> Affects Versions: 2.17.0
> Reporter: Gary Tully
> Priority: Minor
>
> The implementation of the paged browser creates a browser iterator and
> searches from the start for each page contents. It wold be better if it was
> possible to jump right in. Especially when messages are not in memory, ie:
> address limit has caused paging.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
