Skip to main content

Why DataSet.Load and DataTable.Load - very slow ?

The DbDataReader object just reads data from database objects. 

The DbDataAdapter.Fill method reads data and caches them in the DataSet object. 

The DataTable.Load method fills a DataTable with values from a data source using the supplied IDataReader and creates constraints. 

The DataSet.Load method fills a DataSet with values from a data source using the supplied IDataReader, using an array of DataTable instances to supply the schema and namespace information. It creates constraints and tables for represeting data. 

In other words, the Load methods require more time, because they make more operations with data.

Comments

  1. PengMarch 26, 2012 at 10:13 AM

    Testing Data : during tests of SELECT command that DataSet.Load and DataTable.Load methods are much slower compared to other methods of reading data (using DbDataReader or with DbDataAdapter.Fill method). I've got following times:

    Data read with DbDataReader object:
    - Time: 2671.875ms
    Data read with DataSet.Load method:
    - Time: 11546.875ms
    Data read with DataTable.Load method:
    - Time: 11437.5ms
    Data read using DbDataAdapter.Fill method:
    - Time: 3125ms

    In each test 90564 rows were read from database (from two tables) and stored into data set (into two data tables). In DbDataReader's test, data tables were created and filled row-by-row with DataTable.LoadDataRow method.

    Clearly Load methods are almost 5 times slower. Is there any explanation for this. At the beginning I thought that this slow down is caused by constraints checking but disabling it (setting EnforceConstraints property of DataSet object to false) didn't change anything.

    ReplyDelete

Post a Comment

Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold  highlighted in example below) which resolve the problems.   example: <band height="20" splitType="Stretch" > <textField isStretchWithOverflow="true" pa...
4 comments
Read more

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know. Symptom: 1.        The JVM became Out of memory when creating big consumption report 2.        Those JRTemplateElement-instances is still there occupied even if I logged out the system Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.     The clearobjects() method in ReportThread class has not been triggered when logging out Action I tried:      About the Virtualizer: 1.     Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.     Not use any FileVirtualizer for c...
1 comment
Read more

JasperReports - Configuration Reference

Data Source / Query Executer net.sf.jasperreports.csv.column.names.{arbitrary_name} net.sf.jasperreports.csv.date.pattern net.sf.jasperreports.csv.encoding net.sf.jasperreports.csv.field.delimiter net.sf.jasperreports.csv.locale.code net.sf.jasperreports.csv.number.pattern net.sf.jasperreports.csv.record.delimiter net.sf.jasperreports.csv.source net.sf.jasperreports.csv.timezone.id net.sf.jasperreports.ejbql.query.hint.{hint} net.sf.jasperreports.ejbql.query.page.size net.sf.jasperreports.hql.clear.cache net.sf.jasperreports.hql.field.mapping.descriptions net.sf.jasperreports.hql.query.list.page.size net.sf.jasperreports.hql.query.run.type net.sf.jasperreports.jdbc.concurrency net.sf.jasperreports.jdbc.fetch.size net.sf.jasperreports.jdbc.holdability net.sf.jasperreports.jdbc.max.field.size net.sf.jasperreports.jdbc.result.set.type net.sf.jasperreports.query.chunk.token.separators net.sf.jasperreports.query.executer.factory.{language} net.sf.jasperreports.xpath....
Post a Comment
Read more