Dear Jonathan,
> I suspect that part of the reason for this is that cpu time spent in the
> maxima process is not counted by 'time'. (Because it is going on in a
> different process.)
OK, this explains why there is some difference of CPU and Wall time.
However, it does not explain why the differ
On Sat, 2007-10-27 at 12:03 -0700, Simon King wrote:
> Problem was:
> i) When i computed some cup product out of copies of these cocycles,
> then the CPU time was 0.4s, but the Wall time 2.2s. I think this is an
> inacceptable overhead.
I suspect that part of the reason for this is that cpu tim
Dear Mike,
> > I don't think that anything is really going wrong. There is overhead
> > when talking to Maxima through the pexpect interface. You should post
> > the code you are running to see if it can be optimized (with respect
> > to the maxima interface).
>
> In a nutshell, the code was ..
Dear Mike,
On Oct 26, 9:22 am, "Mike Hansen" <[EMAIL PROTECTED]> wrote:
> I don't think that anything is really going wrong. There is overhead
> when talking to Maxima through the pexpect interface. You should post
> the code you are running to see if it can be optimized (with respect
> to the
I don't think that anything is really going wrong. There is overhead
when talking to Maxima through the pexpect interface. You should post
the code you are running to see if it can be optimized (with respect
to the maxima interface).
--Mike
--~--~-~--~~~---~--~~
Dear Sage team,
On Oct 25, 11:42 pm, Simon King <[EMAIL PROTECTED]> wrote:
> Then i tried "prun", and i found that for a couple of functions the
> time per call dramatically went up. Here, for example, two versions of
> the same line returned by prun:
> For the first iteration:
> 1140.
