[infinispan-issues] [JBoss JIRA] (ISPN-3937) Investigate the memory usage of JDBC cache stores when processing a large result set

[Dan Berindei (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950733#comment-12950733 ] 

Dan Berindei commented on ISPN-3937:
------------------------------------

The fetch size is already exposed in the JDBC store configuration, so a user could work around the issue with {{storeBuilder.table().fetchSize(Integer.MIN_VALUE)}}. MySQL 5.0.2+ also has a {{useCursorFetch=true}} connection property that allows the driver to use any fetch size, not just Integer.MIN_VALUE: http://dev.mysql.com/doc/connector-j/en/connector-j-reference-configuration-properties.html

It would be nice to have a better behaviour by default, but I'm not sure what would be the best choice. If the connection property really works, I think we could require the user to set it, and warn on startup if it's not 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
>          Components: Core, Loaders and Stores
>    Affects Versions: 6.0.0.Final
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>             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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira