same for FB2.5 and FB3.0 IXA_WPLATA__KONTRAHENT__PK DYR_ID 0.000007 IXA_WPLATA__KONTRAHENT__PK WPLATA_KONTRAHENT_ID 0.000031 WPLATA_PK DYR_ID 0.058824 WPLATA_PK INSP_ID 0.014925 WPLATA_PK KONTO_ID 0.007353 WPLATA_PK WPLATA_DATA_WYCIAGU 0.000006 WPLATA_PK WPLATA_NR_WYCIAGU 0.000005 WPLATA_PK WPLATA_NR_POZYCJI 0.000000 after second run (cached) - before it was dramatically different timings - but still 0.358s vs 0.031s FB2.5 Executing statement... Statement executed (elapsed time: 0.000s). 0 fetches, 0 marks, 0 reads, 0 writes. 0 inserts, 0 updates, 0 deletes, 164 index, 0 seq. Delta memory: 67064 bytes. Total execution time: 0.031s Script execution finished. FB3.0 Executing statement... Statement executed (elapsed time: 0.000s). 0 fetches, 0 marks, 0 reads, 0 writes. 0 inserts, 0 updates, 0 deletes, 131297 index, 0 seq. Delta memory: 386568 bytes. Total execution time: 0.358s Script execution finished. regards, Karol Bieniaszewski W dniu 2015-11-13 10:09:30 użytkownik <[email protected]> napisał: Karol, > CREATE INDEX IXA_WPLATA__KONTRAHENT__PK ON WPLATA > (WPLATA_KONTRAHENT_ID,DYR_ID); > statistics both 0.000007 > CONSTRAINT WPLATA_PK PRIMARY KEY > (DYR_ID) > statistics both 0.000000 Please provide the result for: select rdb$index_name, rdb$field_name, rdb$statistics from rdb$index_segments where rdb$index_name in (‘IXA_WPLATA__KONTRAHENT__PK’, ‘WPLATA_PK’) -------------------------------------------------------------------------- FB2.5 PLAN JOIN (JOIN (JOIN (SORT (JOIN (W INDEX (WARUNKI_FK1), U NATURAL)), UM INDEX (UMOWA_PK)), RD INDEX (RODZAJ_DZIAL_PK)), OJ INDEX (OPLATAJ_PK)) FB3.0 PLAN JOIN (JOIN (JOIN (JOIN (W ORDER WARUNKI_PK, U NATURAL), UM INDEX (UMOWA_PK)), RD INDEX (RODZAJ_DZIAL_PK)), OJ INDEX (OPLATAJ_PK)) And what are the timings? Please also provide number of page fetches for all the queries. Dmitry
------------------------------------------------------------------------------
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
