[
https://issues.jboss.org/browse/ISPN-3937?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-3937:
------------------------------------
Setting the result set type and concurrency shouldn't be a problem.
Are you worried about the lock on the table being held while we are processing the
results? {{process()}} doesn't do that much work on the caller's thread, so our
iteration over the result set should be only slightly slower than the driver's
fetching of the entire result set.
Investigate the memory usage of JDBC cache stores when processing a
large result set
------------------------------------------------------------------------------------
Key: ISPN-3937
URL:
https://issues.jboss.org/browse/ISPN-3937
Project: Infinispan
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Core, Loaders and Stores
Affects Versions: 6.0.0.Final
Reporter: Dan Berindei
Assignee: Pedro Ruivo
Priority: Critical
Fix For: 7.0.0.Final
Iterating over a huge ResultSet with MySQL seems to keep all the rows in memory:
https://community.jboss.org/message/854402
We should investigate whether we can limit the memory usage to a fixed amount and whether
this affects other drivers as well.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)