Hi. I'm working with Masood. When profiling an explained (MAL) version of TPCH Query 1 with stethoscope, we noticed something strange, and would appreciate your comments. First, the MAL program seems to take longer by about 75% (10 to 15 seconds on a given server) to produce output when run at TPCH scale factor 100. (We have similar results at other scale factors.) Second, the program doesn't produce output until about 10-15 seconds after completing sql.exportResult() when run as MAL, but does so immediately after completing sql.exportResult() when run as SQL. There doesn't seem to be anything going on in that final 10-15 second interval in the MAL program, at least according to stethoscope. What might be happening during that time?
Perhaps
naively, we imagined that the MAL and SQL timings would be about the same.
Thanks,
Steve
From: Martin Kersten <Martin.Kersten@cwi.nl> To: users-list@monetdb.org Sent: Fri, May 17, 2013 5:35:50 PM Subject: Re: Using something like "trace" within the MAL interpreter
For MAL
programs one can use something like: profiler.activate("ISTestmrw"); profiler.setAll(); profiler.openStream(); profiler.start(); ...MAL program to follow.... profiler.stop();