Garrett Smith wrote:

123456789012345678901234567890123456789012345678901234567890123456789012

Does anyone have some guidance on approaches for optimizing database performance?

I realize this is a pretty broad question :)

More specifically, I'm running a simple query

select max(date) from metric

on a table with 21 million rows (or whatever you call them in Monet). It's taking quite a bit longer than I'd expect, given a typically indexed column. Given the fact that there is no (b-tree) index, the underlying engine has to perform a scan to find the maximum. This entails a linear scan over 21M elements in the current implementation.

On an "explain" I see that there's no difference between the plan with or without the presence of an index on 'date'. Per the SQL index docs, I see that indexes are more of a hint to Monet and they're often ignored.

Cool.

But what happens when I want to fix what seems to be a configuration problem with my database/schema?

Thanks!

Garrett

------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users