This issue tracker is closed. Please visit UPPAAL issue tracker at Github instead.

Bug 21

Summary: Statistics about runtime, memory usage, etc.
Product: UPPAAL Reporter: Gerd Behrmann <behrmann>
Component: EngineAssignee: Gerd Behrmann <behrmann>
Status: ASSIGNED ---    
Severity: enhancement CC: marius
Priority: P2    
Version: unspecified   
Hardware: All   
OS: All   
Architecture:

Description Gerd Behrmann 2003-07-02 11:14:56 CEST
I would be nice if we could provide statistics about runtime, memory usage, etc.
This should be provided in both the GUI and in verifyta.
Comment 1 Gerd Behrmann 2005-05-09 14:58:38 CEST
Some basic statistics can now be extracted from verifyta by using the -u option.
More options will be added over time. 
Comment 2 Gerd Behrmann 2005-05-11 12:12:07 CEST
Clarification: This bug is about showing statistics both at runtime (during verification) and after 
verification has completed.
Comment 3 Marius Mikučionis 2007-06-01 18:05:45 CEST
I made a small program in Java to provide functionality similar to memtime:
http://www.cs.aau.dk/~marius/sysmon/

It works in Windows and Linux. Others (Solaris, Mac?) need system manual and a bit more work.

So the plan is to eventually integrate it into progress dialog of Uppaal GUI.
Comment 4 Marius Mikučionis 2007-06-06 12:21:34 CEST
I've got some runtime statistics:
http://www.cs.aau.dk/~marius/verification.png

Could you be more specific what information is interesting?
I see only pwlist statistics available as "load" :-/

For verification completion I guess we need:
times: total wall-clock time, user time, kernel/system time;
and memory peaks: virtual, resident.

However, I am not sure how display it in case several properties are verified.
Comment 5 Marius Mikučionis 2008-05-01 19:01:34 CEST
this is fixed on trunk some time ago, 
unless there is something more you want to be displayed :-)
Comment 6 Marius Mikučionis 2010-08-18 12:23:49 CEST
The memory usage statistics is implemented in server but not reported in verifyta.
I could find some time to nail this since I did the server part.
(feel free to assign this bug to me)