Hi Good engineer practice would call for a series of smaller experiences with 100000, 1.000000, 10.000.000,.... to measure your query/update load and extrapolate from that You can watch progress using the stethoscope tool, there is no a priori knowledge (costmodel) to predict how long it will run. regards, Martin On 17/06/14 12:54, Joe Wass wrote:

I'm running the following query over a database of 1,000,000,000 items.

insert into date_aggregate (count, a, date) select count(date) as count, a, date, from input group by date, a order by date;

I expect it to take a certain length of time, but I have no way of knowing how long.

The system queue table has a 'null' estimate. All I know from that table is that the query is running. Is there a way to get any more information about its progress?

I would be happy to just wait, but I don't know if I should be waiting for hours or days or weeks. The monetdbd process is only using 14% CPU (on a 6 core machine) and 14% RAM (the machine has 7GB and lots of SSD swap). My machine is basically idling when I want it to run as fast as possible. Running Jan2014-SP2, 64-bit on Ubuntu 14.04.

Any hints about measuring progress and improving resource utilisation?

Joe

_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list