Subject | FB slow |
---|---|
Author | Adrian Roman |
Post date | 2002-07-12T19:10:36Z |
Hi,
I have more info on this issue.
The same thing is happening with FB 1.0 and IB 6.02. OS is Windows 2000
Pro, latest SP.
The computer is a PIV 1.9 GHz, 512 M RDRAM, 2 HDD in Raid 0, both at 7200.
I imported a table with about 30.000 records in a dialect 3 database, with
8096 block size.
I just wanted to try it out to see how well it handles transactions, long
updates. I'm investigating it how feasible is to use it to implement an
accounting application.
I started an update wich modifies a field for all 30000 records. It takes
only a couple of seconds. After that, without commiting the transaction, I
change the update statement to change the same field on all records, but
with a different value. This can take even 10 minutes to complete. Rollback
after that sometimes goes fast (several seconds), sometimes is slow, but not
that slow as performing the update.
I know I should keep transactions as short as possible, but this is only for
benchmarking and robustness testing. I want to stress it before implementing
the application, or else I might be the one stressed :-)
PS
By the way, talking about benchmarking, I tried also SAPDB. It's pretty
impressive! It also have logging and incremental backups.
I imported the same 30000 table records in a SAPDB database, and I did an
update query that updated one field in 104 records out of 30000. The
execution time was about 50 ms.
The same thing for Interbase was 9 ms! No indexes were used.
Adrian Roman
I have more info on this issue.
The same thing is happening with FB 1.0 and IB 6.02. OS is Windows 2000
Pro, latest SP.
The computer is a PIV 1.9 GHz, 512 M RDRAM, 2 HDD in Raid 0, both at 7200.
I imported a table with about 30.000 records in a dialect 3 database, with
8096 block size.
I just wanted to try it out to see how well it handles transactions, long
updates. I'm investigating it how feasible is to use it to implement an
accounting application.
I started an update wich modifies a field for all 30000 records. It takes
only a couple of seconds. After that, without commiting the transaction, I
change the update statement to change the same field on all records, but
with a different value. This can take even 10 minutes to complete. Rollback
after that sometimes goes fast (several seconds), sometimes is slow, but not
that slow as performing the update.
I know I should keep transactions as short as possible, but this is only for
benchmarking and robustness testing. I want to stress it before implementing
the application, or else I might be the one stressed :-)
PS
By the way, talking about benchmarking, I tried also SAPDB. It's pretty
impressive! It also have logging and incremental backups.
I imported the same 30000 table records in a SAPDB database, and I did an
update query that updated one field in 104 records out of 30000. The
execution time was about 50 ms.
The same thing for Interbase was 9 ms! No indexes were used.
Adrian Roman