Subject | Re: Firebird 2.0 Indexing (Cont.) vs. PostgreSQL |
---|---|
Author | buppcpp |
Post date | 2005-06-02T19:59:09Z |
Retested and made some configuraion changes to Firebird (FB was
using more memory than it should).
I have now ran test against PostgresSQL (since most of you felt that
a wasn't comparing apples to apples)
Same Table, Data and Indices are in both Databases.
Both Databases were ran on the same machine.
I didn't make ANY changes to the configuration file of PostgresSQL
(didn't know what most of them were for.)
More Info on the table layout can be found here:
http://groups.yahoo.com/group/firebird-support/message/61124?
threaded=1
NOTE: The computer was rebooted after each run.
SELECT COUNT(*) FROM myTable;
PG = 0.52 secs FB = 1.38 min
SELECT DISTINCT store_no FROM myTable;
PG = 0.51 secs FB = 1.31 min
SELECT store_no FROM myTable GROUP BY 1;
PG = 0.27 secs FB = 2.12 min
As you can see, FB is running better than before, but it still runs
much worst than PostgresSQL (without ANY configuration changes)
GROUP BY are terrible in FB !!
using more memory than it should).
I have now ran test against PostgresSQL (since most of you felt that
a wasn't comparing apples to apples)
Same Table, Data and Indices are in both Databases.
Both Databases were ran on the same machine.
I didn't make ANY changes to the configuration file of PostgresSQL
(didn't know what most of them were for.)
More Info on the table layout can be found here:
http://groups.yahoo.com/group/firebird-support/message/61124?
threaded=1
NOTE: The computer was rebooted after each run.
SELECT COUNT(*) FROM myTable;
PG = 0.52 secs FB = 1.38 min
SELECT DISTINCT store_no FROM myTable;
PG = 0.51 secs FB = 1.31 min
SELECT store_no FROM myTable GROUP BY 1;
PG = 0.27 secs FB = 2.12 min
As you can see, FB is running better than before, but it still runs
much worst than PostgresSQL (without ANY configuration changes)
GROUP BY are terrible in FB !!