Issue422

Title include peak memory info in progress reports
Priority wish Status resolved
Superseder Nosy List jendrik, malte
Assigned To jendrik Keywords
Optional summary

Created on 2014-02-16.17:52:14 by malte, last changed by jendrik.

Messages
msg3146 (view) Author: jendrik Date: 2014-04-25.23:54:43
All branches I'm currently working on either need no experiments or already have 
experiments using the old MyExperiment wrapper. Therefore, I included the new 
common_setup.py in this branch. The branch has been merged and pushed.
msg3089 (view) Author: malte Date: 2014-03-25.17:10:32
Is there a point in having experiments for this?
I would say: if it works on one task, it's fine.

I see the point of improving common_setup.py, but shouldn't we do this in the
context of a task that actually needs experiments?
msg3088 (view) Author: jendrik Date: 2014-03-25.15:07:47
I opened a pull request at 
<https://bitbucket.org/jendrikseipp/downward/pull-request/13/issue422-memory-
logging-and-common_setuppy/diff>.
msg3079 (view) Author: jendrik Date: 2014-03-17.14:52:43
I'll use this issue for improving the experiment scripts.
msg2977 (view) Author: malte Date: 2014-02-16.17:52:14
It would be nice to have a more regular update on peak memory usage during
search, e.g. in the "progress evaluator" output.
History
Date User Action Args
2014-04-25 23:54:43jendriksetstatus: reviewing -> resolved
messages: + msg3146
2014-03-25 17:10:32maltesetmessages: + msg3089
2014-03-25 15:07:47jendriksetstatus: chatting -> reviewing
messages: + msg3088
2014-03-17 14:52:43jendriksetassignedto: jendrik
messages: + msg3079
2014-03-03 19:58:32jendriksetnosy: + jendrik
2014-02-16 17:52:14maltecreate