just restarting monetdb wont do it (OS will still keep in memory the data), you will also need to clean the memory, for example alloc all memory space, write 1's and then free again the memory. Swapnil, which version of monetdb are you using? IMO, 11 seconds vs. 30 milliseconds is too much of a difference to be just I/O. But maybe I am wrong, maybe your dbfarm is on a network? On Fri, Nov 30, 2012 at 12:42 PM, Charalampos Nikolaou wrote:

I think the reason is that for the first query the time is spent mainly for loading your table in main memory. Then, the second query has only the overhead of computing the sum over column V1.

To see this, you can run the query, restart monetdbd, and then run the query again. You should get similar performance to that of the first run.

Babis

On Fri, Nov 30, 2012 at 1:29 PM, swapnil joshi wrote:

...

Hi Stefan, If monetdb doesn't maintain any caching then when i am creating test1 database which contain demo table which contain 100 million records.

When first time i am executing "SELECT SUM(V1) FROM DEMO;" monetdb gives me result in (11.4s) when immediate i am trying to execute same query "SELECT SUM(V1) FROM DEMO;" It gives me result in (31.065ms)

How / why this happen?

I have also checked my OS memory cache and I have erased OS Memory cache. Now, I am trying same query "SELECT SUM(V1) FROM DEMO;" now also he take same time in milliseconds approximate(30.723ms)

why he first time take lot of time and every next time he take negligible time.

I hope you will clear my problem related of throughput time.

-- Regards, Swapnil K. Joshi

_______________________________________________ users-list mailing list users-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

_______________________________________________ users-list mailing list users-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list

_______________________________________________ users-list mailing list users-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list