[Maxima] looking for bottlenecks, was: property lisp hack
robert.dodier at gmail.com
Fri Aug 10 14:11:02 CDT 2012
On 2012-08-10, Raymond Toy <toy.raymond at gmail.com> wrote:
> And based on my experience, run_testsuite(time=true) now seems to spend
> quite a bit of time doing numerical evaluation instead of symbolic. But
> rtest_integrate, which seems to take the longest, presumably does a huge
> amount of symbolic work. Not sure what that all means in terms of the
> propery list hack.
If we are looking for places to speed up Maxima, the first place I'd
look is the assume database. I seem to recall that the database is
consulted very often (by ALIKE1? I don't remember for sure) and each
consultation causes many comparisons, including some that seem
nonsensical -- stuff like "is 1b0 greater than 1d0" as I recall. We
could try to reduce the number of consultations and also try to reduce
the time spent on each one.
Second place to look is ALIKE1 itself, since it's called so often.
Third place is the factoring code -- if I'm not mistaken, the long
execution time of some of the test scripts is due to trying to factor
Of course, each of these needs further investigation.
More information about the Maxima