#10903: Update Singular to 3-1-3-3.
---------------------------------------------------------+------------------
Reporter: malb | Owner: tbd
Type: defect | Status:
needs_work
Priority: critical | Milestone:
sage-4.7.2
Component: packages | Keywords:
singular SageDays34 sd34
Work_issues: memory usage | Upstream: N/A
Reviewer: Martin Albrecht, Volker Braun, Simon King | Author:
Burcin Erocal, Martin Albrecht, Volker Braun, Simon King
Merged: | Dependencies:
#11339
---------------------------------------------------------+------------------
Changes (by jdemeyer):
* status: positive_review => needs_work
* work_issues: => memory usage
Comment:
Unfortunately, I discovered another serious issue with the new Singular
(#11339 + #10903): there is an enormous '''virtual memory usage
regression''' in the test
{{{
sage -t -long devel/sage/sage/crypto/mq/sr.py
}}}
It used to need about '''1.2GB''' virtual memory, with the new Singular it
needs '''3.0GB'''. I measured this by setting {{{ulimit -v}}} and
checking whether the test succeeds, for example:
{{{
### The parentheses start a subshell such that the ulimit only affects
### that one command and not the whole shell.
$ ( ulimit -v 2500000; ./sage -t -long devel/sage/sage/crypto/mq/sr.py )
sage -t -long "devel/sage/sage/crypto/mq/sr.py"
[***** 0.000s] # doctest internal
[***** 0.000s] # doctest internal
[00029 0.040s] sr = mq.SR(Integer(1), Integer(1), Integer(1), Integer(4))
[...]
[03326 0.000s] from sage.crypto.mq.sr import AllowZeroInversionsContext
[03327 0.010s] sr = mq.SR(Integer(1),Integer(2),Integer(2),Integer(4))
[03328 0.000s] with AllowZeroInversionsContext(sr):
[03331 0.000s] sr._allow_zero_inversions
[***** 0.000s] # doctest internal
[***** 0.000s] # doctest internal
[***** 0.000s] # doctest internal
[03355 0.010s] from sage.crypto.mq.sr import test_consistency
Singular error: no more memory
System 1604712k:1604712k Appl 1450267k/23501k Malloc 1032k/0k Valloc
1472736k/23501k Pages 368184/0 Regions 2932:2932
halt 14
[114.3 s]
}}}
I don't know whether this issue is upstream or caused by some of the Sage
library patches, but it is certainly serious enough not to merge this
ticket.
As a reference: before this ticket, every test passed with 2.2GB of RAM,
with the most memory used by
{{{
sage -t -long devel/sage/sage/schemes/elliptic_curves/heegner.py
}}}
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10903#comment:88>
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.
