<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 14: Export data into RDBMS table using JDBC Batch update</title><link>https://sourceforge.net/p/cloudbase/feature-requests/14/</link><description>Recent changes to 14: Export data into RDBMS table using JDBC Batch update</description><atom:link href="https://sourceforge.net/p/cloudbase/feature-requests/14/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 17 Sep 2009 03:33:33 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/cloudbase/feature-requests/14/feed.rss" rel="self" type="application/rss+xml"/><item><title>Export data into RDBMS table using JDBC Batch update</title><link>https://sourceforge.net/p/cloudbase/feature-requests/14/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;JDBC batch update is faster than single update per row. I could see 5x performance improvement in some cases on our cluster. I just replace 'executeUpdate( )' with 'addBatch()' and 'executeBatch()'. and I call the 'executeBatch()' per file. and This is a straitforward implementation. I do not consider 'batch size', 'commit size' or something like that. but it works fine so far.&lt;/p&gt;
&lt;p&gt;I think we can configure the batch size for export in Cloudbase's configuration.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">YoungWoo Kim</dc:creator><pubDate>Thu, 17 Sep 2009 03:33:33 -0000</pubDate><guid>https://sourceforge.net99a570e17f846903918b63dd108ef63e46c96138</guid></item></channel></rss>