Comment #4 on issue 3222 by psotny...@gmail.com: Memory problems with the
cache
http://code.google.com/p/sympy/issues/detail?id=3222
The other problem with the cache is that people who don't know about it (or
didn't know, like me) may spend a lot of time using profilers and generally
blaming python (or their own source) for memory leaks.
I found the sympy "cache" concept minutes ago and this solved issues I had
for the last two months (my computations would eat all memory, and I could
not locate the leak using profilers).
Using "SYMPY_USE_CACHE=no" slowed my computations 50x and memory issues
were gone; using clear_cache() periodically fixed memory issues at no
performance cost.
The ideal solution would be that cache would be "on" by default (as it is
now), but would wisely use available memory (who knows, maybe auto-clearing
cache on each garbage collection by default? users would be able to change
this behavior by "SYMPY_USE_CACHE=persistent". Or clearing cache when
available RAM is nearly entirely used - as long as this can be reliably
detected).
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"sympy-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sympy-issues+unsubscr...@googlegroups.com.
To post to this group, send email to sympy-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/sympy-issues.
For more options, visit https://groups.google.com/groups/opt_out.
