[quote=“rencailhc”][quote=“plumber”]You’re using the “time” Linux tool?
If you’re the only user running queries on the box, them the important/relevant time is the “real” time, which is the wall clock time associated with the iquery execution time. It’s the amount of time that passed between when the process ID was created for the iquery program and when it exited. In other words, it’s the time that includes both the iquery processing time, AND the server side processing time. When we time query performance in-house, the real execution time of the overall query is what we look at first. When we want to go deeper, we try to break queries up into smaller sections by looking at how long / how much compute / memory / IO resource, was consumed by each operator in a query plan.
The other two numbers … user and sys … refer to the user space CPU time and the system space CPU time for the iquery process. They’re not really relevant to time the query as they don’t include server-side processing.
Have a look at “man time”.[/quote]
I am wondering which tool you use to check the CPU / memory / IO resources a SciDB query takes. The tool may be like EXPLAIN ANALYZE for postgresql or some linux tool?[/quote]
i use the linux time interface,i think the real time as the execution time.