Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PARI LLL speed depends on PARI stack size #15660

Closed
jdemeyer opened this issue Jan 10, 2014 · 17 comments
Closed

PARI LLL speed depends on PARI stack size #15660

jdemeyer opened this issue Jan 10, 2014 · 17 comments

Comments

@jdemeyer
Copy link

From a doctest in qqbar.py:

sage: x = polygen(AA)
sage: %time QQbar.polynomial_root(x^5 - x - 1, CIF(RIF(0.1, 0.2), RIF(1.0, 1.1))).imag().exactify()
CPU times: user 28.33 s, sys: 0.02 s, total: 28.35 s
Wall time: 28.38 s
sage: pari.allocatemem(1<<30)
PARI stack size set to 1073741824 bytes
sage: %time QQbar.polynomial_root(x^5 - x - 1, CIF(RIF(0.1, 0.2), RIF(1.0, 1.1))).imag().exactify()
CPU times: user 2.70 s, sys: 0.15 s, total: 2.85 s
Wall time: 2.84 s

Upstream: http://pari.math.u-bordeaux.fr/cgi-bin/bugreport.cgi?bug=1653

Depends on #15653
Depends on #15654

Upstream: Fixed upstream, but not in a stable release.

Component: performance

Branch/Commit: u/rws/ticket/15660 @ d484242

Reviewer: Jeroen Demeyer

Issue created by migration from https://trac.sagemath.org/ticket/15660

@jdemeyer jdemeyer added this to the sage-6.1 milestone Jan 10, 2014
@jdemeyer

This comment has been minimized.

@jdemeyer jdemeyer changed the title QQbar minpoly() speed depends on PARI stack size QQbar exactify() speed depends on PARI stack size Jan 10, 2014
@jdemeyer jdemeyer changed the title QQbar exactify() speed depends on PARI stack size QQbar speed depends on PARI stack size Jan 10, 2014
@jdemeyer jdemeyer changed the title QQbar speed depends on PARI stack size PARI LLL speed depends on PARI stack size Jan 10, 2014
@jdemeyer
Copy link
Author

Author: Jeroen Demeyer

@jdemeyer
Copy link
Author

Dependencies: #15653, #15654

@jdemeyer
Copy link
Author

Branch: u/jdemeyer/ticket/15660

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Jan 10, 2014

Branch pushed to git repo; I updated commit sha1. New commits:

8c58208"long time" fixes

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Jan 10, 2014

Commit: 8c58208

@jdemeyer
Copy link
Author

New commits:

7537427Fix conversion of zero p-adics to PARI
a955e45Speed up PARI determinants when stacksize is small
b29b0b7Speed up PARI LLL when stacksize is small
8c58208"long time" fixes

@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.1, sage-6.2 Jan 30, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.2, sage-6.3 May 6, 2014
@rwst
Copy link

rwst commented May 11, 2014

Work Issues: rebase

@rwst
Copy link

rwst commented Jul 13, 2014

Changed branch from u/jdemeyer/ticket/15660 to u/rws/ticket/15660

@rwst
Copy link

rwst commented Jul 13, 2014

Changed commit from 8c58208 to d484242

@rwst
Copy link

rwst commented Jul 13, 2014

New commits:

d484242Merge branch 'develop' into t/15660/ticket/15660

@rwst
Copy link

rwst commented Jul 13, 2014

Changed work issues from rebase to none

@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@jdemeyer
Copy link
Author

Reviewer: Jeroen Demeyer

@jdemeyer

This comment has been minimized.

@jdemeyer
Copy link
Author

comment:14

Fixed by #16997.

@jdemeyer
Copy link
Author

Upstream: Fixed upstream, but not in a stable release.

@jdemeyer
Copy link
Author

Changed author from Jeroen Demeyer to none

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants