hi,

I am using DBISAM Table Component of Version 3.17.

I have created a table of 169 Columns and Record Size is 2515.

i am inserting 7000 records into the table

1) As Local Table (.DAT File Exists in Disk) - Time Taken - 3.40 Seconds approx
2) As Memory Table  - Time Taken - 1 Minute approx

Can Somebody let me know is this difference is because of RAM or Paging?

I have enough RAM of about 2 GB in my machine.

Thanks in Advance.

Regards

S.Ravi

Ravi,

<< I am using DBISAM Table Component of Version 3.17.

I have created a table of 169 Columns and Record Size is 2515.

i am inserting 7000 records into the table

1) As Local Table (.DAT File Exists in Disk) - Time Taken - 3.40 Seconds
approx
2) As Memory Table  - Time Taken - 1 Minute approx

Can Somebody let me know is this difference is because of RAM or Paging? >>

3.17 may be using a smaller internal block size for in-memory files than
later versions as well as re-allocating when growing the file(s), and this
may be contributing to the issue.  3.30 uses a 4096-byte block size when
allocating or reallocating, which may make it slightly faster.  4.x doesn't
do reallocation during a grow, so it is much faster than 3.x in general with
in-memory files, especially when appending a large number of records.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

So is there a workaround for this ?

Thanks
Praveen

Praveen


Move to 3.30 or better 4.24

Roy Lambert