#10975: creation of certain prime finite fields is double dog slow (compared to
Magma)
--------------------------------+-------------------------------------------
Reporter: was | Owner: AlexGhitza
Type: enhancement | Status: new
Priority: critical | Milestone: sage-4.7
Component: basic arithmetic | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
--------------------------------+-------------------------------------------
Comment(by lmartel):
And here is more:
{{{
156 function calls (155 primitive calls) in 33.016 CPU seconds
Ordered by: internal time
ncalls tottime percall cumtime percall filename:lineno(function)
3 24.749 8.250 24.749 8.250 {method 'is_prime' of
'sage.rings.integer.Integer' objects}
1 8.266 8.266 8.266 8.266 {method 'is_prime_power' of
'sage.rings.integer.Integer' objects}
1 0.000 0.000 8.258 8.258
finite_field_prime_modn.py:42(__init__)
3 0.000 0.000 24.749 8.250 arith.py:404(is_prime)
1 0.000 0.000 33.016 33.016 <string>:1(<module>)
1 0.000 0.000 0.000 0.000
integer_mod_ring.py:172(__init__)
}}}
the difference probably comes from proven prime vs pseudo prime...
(and also:
{{{
magma: time IsPrime(10^310 + 733) --> true Time: 28.130
}}}
)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10975#comment:3>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
