Issue210

Title investigate memory usage of translator
Priority wish Status resolved
Superseder Nosy List gabi, malte
Assigned To Keywords translator
Optional summary

Created on 2011-01-18.17:54:55 by malte, last changed by gabi.

Messages
msg3663 (view) Author: gabi Date: 2014-10-06.09:15:21
I am fine with closing this issue and therefore do so.
msg3643 (view) Author: malte Date: 2014-10-04.20:05:10
We openen this three years ago but apparently never felt this would be worth
bothering. :-) Gabi, do you think this should remain an open issue? Otherwise
I'd just close it.
msg1201 (view) Author: malte Date: 2011-01-18.17:54:55
We sometimes get out of memory errors in the translator on the Grid, apparently
even with a 3 GB limit, even though the same task takes less than 2 GB on
alfons. Might be a Python version difference. An example of this is Scanalyzer #28.

Once we can measure memory usage in the translator (see issue209), we should
maybe look into reducing it. Two ideas that might save a lot:

 * in translate.py, remove the untranslated versions of the operators once
   they have been processed
 * if the same atom/literal is used in multiple places, don't use a copy,
   but reuse the same object.
History
Date User Action Args
2014-10-06 09:15:21gabisetstatus: chatting -> resolved
messages: + msg3663
2014-10-04 20:05:10maltesetmessages: + msg3643
keyword: + translator
2011-01-18 17:54:55maltecreate