Hi !

The problem detected by Nadir has been logged in bugs.infobright.org (http://bugs.infobright.org/ticket/1916, though I do not know if it is visible publicly). It seems to stay there not fixed. Strange…
——

I checked it in practice and the problem of growing files sizes when loading by small chunks has been fixed. Can you tell more precisely what problem you have? And which IB version you use?

Thanks both for your replies. As stated earlier we are using ICE 4.0.3, and we notice big increase in size of data files when we do bulk import with few rows at a time. And that size decreases sharply on exporting the whole database and re-importing it back. Its the same issue as reported in this post.

Which version did you checked it on, Janusz? Please let me know if this has been fixed in any newer version. 

Thanks,
Puneet

Hi !

I tried 4.0.5. Could you post the results of “ls -l” on the table directory after importing by a few rows, and then after a bulk import ?

I verified it using the scenario supplied with the previously reported bug (the one reported as “unfixed”) and in practice it is fixed. AFAIK the problem has been fixed in 2010 using a different bug report. By looking at the “ls -l” output we will be able to understand the situation.

Thanks for your response, Janusz. I tried testing it with 4.0.5, and I am still seeing similar issue. I added 9000 rows to my Data table (3 rows at a time) and size of table directory went up to 7.4 MB. After export + import, it reduced to 1.6 MB. I have attached the results of ‘ls -l’ on table directory as you asked for, one before bulk import (by importing 3 rows at a time), and one after bulk import.  Let me know your thoughts on it, or if there is anything else you need.

Thanks,
Puneet

Hi !

You are right. The problem reported by Nadir, now by you, is not fixed in ICE (fixed for IEE). I suggest you can create a ticket in bugs.infobright.com. Please refer to an existing ticket http://bugs.infobright.org/ticket/1916 created by Nadir just reminding that the problem is still unsolved.

I have created a new bug within bugs.infobright.com for this issue.  Please reference: http://bugs.infobright.com/ticket/2112