#16380: improve startup time of libGAP
----------------------------------------+------------------------
Reporter: dimpase | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.3
Component: interfaces | Resolution:
Keywords: libgap, startup time | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
----------------------------------------+------------------------
Changes (by dimpase):
* cc: wdj (added)
Old description:
> currently libGAP loads slower than GAP with pexpect interface.
> {{{
> $ ./sage --nodotsage
> Sage Version 6.3.beta1, Release Date: 2014-05-13 │
> sage:
> sage: gap("1")
> 1
> sage:
> Exiting Sage (CPU time 0m0.22s, Wall time 0m21.87s).
> Exiting spawned Gap process.
> nash:sage dima$ ./sage --nodotsage
> Sage Version 6.3.beta1, Release Date: 2014-05-13 │
> sage: libgap("1")
> "1"
> sage:
> Exiting Sage (CPU time 0m7.06s, Wall time 0m16.95s).
> }}}
>
> About extra 7 sec on a Core2 `x86_64` machine, at least according to the
> CPU time report, which might be lying(?).
>
> The main issue is most probably in ability to save/load a GAP workspace,
> which is absent in libGAP at the moment. See also
> https://bitbucket.org/vbraun/libgap/issue/2/workspace-support
New description:
currently libGAP loads slower than GAP with pexpect interface.
{{{
$ ./sage --nodotsage
Sage Version 6.3.beta1, Release Date: 2014-05-13 │
sage:
sage: gap("1")
1
sage:
Exiting Sage (CPU time 0m0.22s, Wall time 0m21.87s).
Exiting spawned Gap process.
nash:sage dima$ ./sage --nodotsage
Sage Version 6.3.beta1, Release Date: 2014-05-13 │
sage: libgap("1")
"1"
sage:
Exiting Sage (CPU time 0m7.06s, Wall time 0m16.95s).
}}}
About extra 7 sec on a Core2 `x86_64` machine, at least according to the
CPU time report, which might be lying(?).
The main issue is in saving/loading a GAP workspace, which is not done by
`libGAP` at the moment. See also
https://bitbucket.org/vbraun/libgap/issue/2/workspace-support
--
Comment:
The workspace to load should be created by `libGAP`, and not by "normal"
`GAP`. Then it all works.
Should we mimic the way "normal" GAP deals with the workspaces? Or are
there other/better ideas?
--
Ticket URL: <http://trac.sagemath.org/ticket/16380#comment:4>
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.
