Main menu
You are here
Timing reported by summary() seems to be wrong
Thu, 02/04/2010 - 11:28 — neale
Running a model reported
frontend elapsed time: 0.7429769 secs
backend elapsed time: 2.985495 mins
looks ok but in fact I system.time'd the run and it reported:
> system.time(multivTwinSatFit<-mxRun(multivTwinSatModel))
Running multivTwinSat
user system elapsed
177.301 0.608 179.884
so there are some 175 seconds missing from the tally.
Also, the results from a run with @independent=T under snowfall are different and seem to be basically reporting zero seconds for backend elapsed time.
Reporter:
Created:
Thu, 02/04/2010 - 11:28
Updated:
Thu, 03/11/2010 - 12:55
- Log in or register to post comments
Printer-friendly version
Comments
#1
Umm, the backend elapsed time is reported in minutes. 3 minutes is about 180 seconds. But the elapsed time numbers are wrong when using snowfall. I'm not sure whether to add up all the times for the independent processes (but that is compute time not elapsed time), or just report elapsed time in which case I cannot separate front-end and back-end time.
#2
> 2.98549560
[1] 179.1297
> (2.98549560)+0.7429769
[1] 179.8727
Looks pretty close to me.
Not sure what's wrong with the snowfall reporting.
#3
Yup, my duh, didn't see the different format time metric (too conditioned by Mx1 which reports time in the same metric DD:HH:MM:SS:hh). Am not keen on the automagic switching of units, tbh.
#4
I changed summary() output to show frontendTime, backendTime, and independentTime. The third value is the total time spend executing independent submodels (that includes the frontendTime + backendTime for the submodels). I also added the option submodels = FALSE to the summary() function. It will ignore independent submodels when computing the summary (much faster). See ?summary for help.
#5
Seems to be working.
#6
Automatically closed -- issue fixed for 2 weeks with no activity.