#15654: PARI discriminant speed depends on stack size
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status: needs_review
Priority: critical | Milestone: sage-6.1
Component: performance | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers:
Report Upstream: Reported | Work issues:
upstream. Developers deny it's a | Commit:
bug. | a955e45e17cdbd40d24a103ef7903c5f970b24a3
Branch: | Stopgaps:
u/jdemeyer/ticket/15654 |
Dependencies: #15653 |
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
Replying to [comment:9 roed]:
> More generally, are there other places in Sage where we should be more
aggressive about increasing the Pari stack size? If someone is using Pari
nontrivially, our current stack size seems too small. Should we increase
the stack whenever a user does certain operations signaling that they're
going to be using Pari extensively (e.g. create a number field of degree
larger than 4, take the discriminant of a polynomial of large degree...)?
We could ''detect'' the problem by adding some code to `gerepile...()` to
count the number of garbage collections. We could for example give a
warning if more than N happen per second (for a suitable value of N).
--
Ticket URL: <http://trac.sagemath.org/ticket/15654#comment:11>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
