Claus Pedersen
Member³
I have a table with approx. 21000 rows. The columns are a mix of the types number, varchar2, date and a single clob column.
I select all rows in an SQL window.
If I select a single number column, PLD 32 bit will select all rows in 4.5 sec. PLD 64 bit executes the same select in 9.3 sec.
PLD 64 bit is a factor 2 (or 5 seconds) slower.
I now select all columns (excluding the CLOB column). The results are:
32 bit: 14.5 sec.
64 bit: 20.1 sec.
PLD 64 bit is still approx. 5 seconds slower.
I now select the CLOB column only. The results are:
32 bit: 31 sec.
64 bit: 273 sec.
64 bit is a factor 9 (!) slower when selecting CLOB columns.
The max. length of the clob column is approx. 1200 bytes, so it is probably not the amount of data that slows down the query time.
I have made a test script with a cursor selecting the clob column from all rows and this executes in approx. 0.2 sec. both in 32 bit and 64 bit, so it does not seem to be a driver problem.
It seems that the bottle neck lies inside PLD 64 bit.
I select all rows in an SQL window.
If I select a single number column, PLD 32 bit will select all rows in 4.5 sec. PLD 64 bit executes the same select in 9.3 sec.
PLD 64 bit is a factor 2 (or 5 seconds) slower.
I now select all columns (excluding the CLOB column). The results are:
32 bit: 14.5 sec.
64 bit: 20.1 sec.
PLD 64 bit is still approx. 5 seconds slower.
I now select the CLOB column only. The results are:
32 bit: 31 sec.
64 bit: 273 sec.
64 bit is a factor 9 (!) slower when selecting CLOB columns.
The max. length of the clob column is approx. 1200 bytes, so it is probably not the amount of data that slows down the query time.
I have made a test script with a cursor selecting the clob column from all rows and this executes in approx. 0.2 sec. both in 32 bit and 64 bit, so it does not seem to be a driver problem.
It seems that the bottle neck lies inside PLD 64 bit.
