Oracle JDBC prefetch: how to avoid running out of RAM

发布时间:2020-09-05 发布网站:编程之家
编程之家收集整理的这篇文章主要介绍了Oracle JDBC prefetch: how to avoid running out of RAM编程之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。

Using Oracle java JDBC (ojdbc6,loading a query with many rows takes forever (high latency environment. This is apparently the default prefetch in Oracle JDBC is default size "10" which requires a round trip time once per 10 rows. I am attempting to set an aggressive prefetch size to avoid this.

PreparedStatement stmt = conn.prepareStatement("select * from tablename"); statement.setFetchSize(10000); ResultSet rs = statement.executeQuery(); 

This can work,but instead I get an out of memory exception. I had presumed that setFetchSize would tell it to buffer "that many rows" as they come in,using as much RAM as each row requires. If I run with 50 threads,even with 16G of -XMX space,it runs out of memory. Feels almost like a leak:

Exception in thread "main" java.lang.OutOfMemoryError: Java heap space at java.lang.reflect.Array.newArray(Native Method) at java.lang.reflect.Array.newInstance( at oracle.jdbc.driver.BufferCache.get( at oracle.jdbc.driver.PhysicalConnection.getCharBuffer( at oracle.jdbc.driver.OracleStatement.prepareAccessors( at oracle.jdbc.driver.T4CTTIdcb.receiveCommon( at oracle.jdbc.driver.T4CTTIdcb.receive( at oracle.jdbc.driver.T4C8Oall.readDCB( at oracle.jdbc.driver.T4CTTIfun.receive( at oracle.jdbc.driver.T4CTTIfun.doRPC( at oracle.jdbc.driver.T4C8Oall.doOALL( at oracle.jdbc.driver.T4CPreparedStatement.doOall8( at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe( at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe( at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout( at oracle.jdbc.driver.OraclePreparedStatement.executeInternal( at oracle.jdbc.driver.OraclePreparedStatement.executeQuery( at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery( .... 

What can I do to still get prefetch but not run out of RAM? What is going on?

The closest related item on SO is this:


Basically,oracle‘s default strategy for later ojdbc jars is to "pre allocate" an array per "prefetch" row that accomodates for the largest size conceivably possible to return from that query. So in my case I had some VARCHAR2(4000) in there,so 50 threads * 3 columns of varchar2‘s * 4000 was adding up to more than gigabytes of RAM [yikes]. There does not appear to be an option to say "don‘t pre allocate that array,just use the size needed." Ojdbc even keeps these preallocated buffers around between preparedstatements so it can reuse them. Definitely a memory hog.

The fix was to determine the maximum actual column size,then replace the query with (assuming 50 is the max size) select substr(column_name,50) as well as profile and only use as high of setFetchSize as actually made significant speed 

Other things you can do: decrease the number of prefetch rows,increase Xmx parameter,only select the columns you need.

Once we were able to use at least prefetch 400 [make sure to profile to see what numbers are good for you,with high latency we saw 
 ments up to prefetch size 3-4K] on all queries,performance 
 d dramatically.

I suppose if you wanted to be really aggressive against sparse "really long" rows you might be able to re-query when you run into these [rare] rows.

Details ad nauseum here



以上是编程之家为你收集整理的Oracle JDBC prefetch: how to avoid running out of RAM全部内容,希望文章能够帮你解决Oracle JDBC prefetch: how to avoid running out of RAM所遇到的程序开发问题。



微信公众号搜索 “ 程序精选 ” ,选择关注!

微信公众号搜索 “ 程序精选 ”