Hi Ruben,
Some database details:
Tables: 228
Views: 75
The "table2" table is one of the biggest in our database
Number of columns: 118
If you look at the code in SequoiaResultSetMetaDataFactory, we fetch a
number of metadata individually for each column. Unfortunately it seems
that the Postgres driver transforms every call into an inefficient query
which shows this poor performance.
The metadata cache will certainly improve performance but not of the
first request. The Postgres driver could probably be improved to fetch
all metadata at once.If there is metadata that you never access, you can
create your own ResultSetMetaDataFactory by removing the info your don't
need from the SequoiaResultSetMetaDataFactory.
Hope this helps,
Emmanuel
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [email protected]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
