#19585: Improve efficiency of calling GAP functions
-------------------------------------+-------------------------------------
Reporter: jaanos | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.10
Component: interfaces | Resolution:
Keywords: GAP functions | Merged in:
interface | Reviewers: Travis Scrimshaw
Authors: Janoš Vidali | Work issues:
Report Upstream: N/A | Commit:
Branch: | f59926575333e34976901f92c1f070e0c168a0b9
u/tscrim/improve_calling_gap_function-19585| Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by nbruin):
Replying to [comment:16 dimpase]:
> interestingly, libGAP is quite slow here.
...
> I guess there handling of `P` and `S` on the Sage side is not optimal...
That is one possibility. It could also be that libGap gets compiled with
different optimization settings and/or that the memory manager underneath
is different and affects execution. It could really be worthwhile if
someone knowledgeable about libGap would run some of these examples
through a profiler (gperftool perhaps?) and compare the execution profiles
between Gap and libGap.
--
Ticket URL: <http://trac.sagemath.org/ticket/19585#comment:17>
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/d/optout.
