Hi,
On Mon, May 08, 2017 at 09:23:30PM +0200, Vincent Delecroix wrote:
> Hello Marcelo,
>
> Please have a look at
>
> https://trac.sagemath.org/ticket/19519
If we could have a similar feature for memory usage, that could be
interesting, see e.g. https://trac.sagemath.org/ticket/22684
Ciao,
T
thanks David and Vincent for your interesting insights :) i'll start to
have a look..
1 motivation for this feature: when you have two or more implementations of
the same problem and want to compare them based on running times.
El lunes, 8 de mayo de 2017, 21:24:10 (UTC+2), vdelecroix escribió
Hello Marcelo,
Please have a look at
https://trac.sagemath.org/ticket/19519
Vincent
On 08/05/2017 10:35, mforets wrote:
Hi,
i wanted to know if there is a keyword that can be put next to a doctest to
measure performance with respect to computation time, like:
sage: possibly_long_calculatio
On Mon, May 8, 2017 at 5:24 AM, mforets wrote:
> ok! i've tested exporting SAGE_TIMEOUT and it does have an effect, for
> example:
>
> **
> Tests run before process (pid=3019) timed out:
> sage: integrate(exp(-x)*sinh(sqrt(x)), x
ok! i've tested exporting SAGE_TIMEOUT and it does have an effect, for
example:
**
Tests run before process (pid=3019) timed out:
sage: integrate(exp(-x)*sinh(sqrt(x)), x, 0, oo,
algorithm='maxima').simplify() ## line 10 ##
**
On Mon, May 8, 2017 at 4:35 AM, mforets wrote:
> Hi,
> i wanted to know if there is a keyword that can be put next to a doctest
> to measure performance with respect to computation time, like:
>
> sage: possibly_long_calculation(..) # timeout 600s
> 0
>
> this is seems item 1) in this thread's O
