Em 21-03-2012 11:01, Joachim Durchholz escreveu:
Am 21.03.2012 06:27, schrieb Saptarshi Mandal:
Anyway, I am curious to know what the energy footprint of the core
sympy algorithms will be. It may be the case that in order to conserve
battery life, we might need to change how certain algorithms are
implemented, leave some sub-expressions un-evaluated, introduce more
laziness in computation, etc. Thesis topic anyone? :P
SymPy's core algorithms are CPU-bound. In other words, I do not see
any specific considerations for mobile SymPy that aren't already
covered by normal optimisation and algorithmic improvements.
One could think about tweaking SymPy's cache algorithm. I.e. make it
less likely to throw away cache entries if the platform is more CPU
than memory constrained. (Assuming cache entries are ever cleared in
SymPy. I don't know whether SymPy does that.)
Look at my site "SymPy for smartphones & tablets", top table :
http://www.robertocolistete.net/Python/SymPy/
Even a Nokia N95 from 2007, with 20MB of free RAM and OMAP2420 (ARM11) @
330 MHz can calculate heavy integrals, etc.
I agree that we can tune SymPy to load faster on smartphones &
tablets, by choosing less modules to be automatically loaded.
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sympy?hl=en.
