[infinispan-issues] [JBoss JIRA] (ISPN-12318) Query.maxResult() ignored during entity loading
[
https://issues.redhat.com/browse/ISPN-12318?page=com.atlassian.jira.plugi...
]
Gustavo Fernandes updated ISPN-12318:
-------------------------------------
Description:
When a query has a maxResult it should not try to load collect all results but rather
restrict it to the requested page size. This causes unnecessary allocations of Strings and
byte[]. In particular, the {{KeyTransformationHandler#stringToKey}} method produces a
large amount of garbage.
Other issue is the default maxResult is not defined consistently: it is 10 for queries
over REST and undefined for embedded and queries over Hot Rod.
was:
When a query has a maxResult it should not try to load all results from the cache but
rather restrict it to the requested page size. This causes unnecessary allocations of
Strings and byte[]. In particular, the {{KeyTransformationHandler#stringToKey}} method
produces a large amount of garbage.
Other issue is the default maxResult is not defined consistently: it is 10 for queries
over REST and undefined for embedded and queries over Hot Rod.
Query.maxResult() ignored during entity loading
-----------------------------------------------
Key: ISPN-12318
URL: https://issues.redhat.com/browse/ISPN-12318
Project: Infinispan
Issue Type: Bug
Components: Embedded Querying
Affects Versions: 12.0.0.Dev03
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
Priority: Critical
When a query has a maxResult it should not try to load collect all results but rather
restrict it to the requested page size. This causes unnecessary allocations of Strings and
byte[]. In particular, the {{KeyTransformationHandler#stringToKey}} method produces a
large amount of garbage.
Other issue is the default maxResult is not defined consistently: it is 10 for queries
over REST and undefined for embedded and queries over Hot Rod.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)