Hi,
Le 12/05/2014 11:45, Emmanuel Charpentier a écrit :
Le vendredi 9 mai 2014 18:31:02 UTC+2, Dima Pasechnik a écrit :
On 2014-05-09, Volker Braun > wrote:
We do have a arm machine in Oxford with more than enough ram (afair
4GB).
Dima did some work on finishing the arm port. In any case,
Arm might soon be a major player in the low-power server market, see e.g.
the recent Opteron A1100 announcement.
On Monday, May 12, 2014 11:45:12 AM UTC+2, Emmanuel Charpentier wrote:
>
> > We do have a arm machine in Oxford with more than enough ram (afair
>> 4GB).
>> > Dima did some work on
Le vendredi 9 mai 2014 18:31:02 UTC+2, Dima Pasechnik a écrit :
>
> On 2014-05-09, Volker Braun > wrote:
> > We do have a arm machine in Oxford with more than enough ram (afair
> 4GB).
> > Dima did some work on finishing the arm port. In any case, its not a ram
> > issue.
> indeed. Please re
leif wrote:
For the record, I just built Sage 6.2 from scratch on a 32-bit (x86)
Linux box with just 2 GB RAM (but of course swap enabled), with FSF GCC
4.8.2* and '-O3', using *three* jobs/threads (although it's just a
single-core), with GNOME running.
[...]
[ptestlong still in progress; this
William Stein wrote:
Does anybody know how much RAM is required to build Sage these days.
With MAKE not set, typing "make" with sage-6.2.rc2 on a VM with 4GB
RAM results in failure (see below). Of course, I'm not using swap,
and of course with swap you can do anything if you're willing to wait
On 2014-05-09, Volker Braun wrote:
> We do have a arm machine in Oxford with more than enough ram (afair 4GB).
> Dima did some work on finishing the arm port. In any case, its not a ram
> issue.
indeed. Please review :)
http://trac.sagemath.org/ticket/15921
>
>
> On Friday, May 9, 2014 1:41:44
On 2014-05-09 14:08, leif wrote:
And probably some build- or patchbots should run the tests with 'ulimit
-v $SAGE_DOCTEST_MEMORY_CUTOFF' by default.
Totally +1.
I always did that with a limit of 2.5GB.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" g
Jeroen Demeyer wrote:
On 2014-05-09 10:55, Julien Puydt wrote:
But personally, I don't consider RAM usage by doctests an issue.
Perhaps because you don't use old or limited computers?
No, because I think that doctest coverage is more important than memory
usage of doctests. It is perfectly po
On Tuesday, May 6, 2014 12:14:50 AM UTC+2, William wrote:
>
> RAM results in failure (see below). Of course, I'm not using swap,
> and of course with swap you can do anything if you're willing to wait.
>
Unix needs swap to back anon mmaps even if nothing is actually written to
disk. Not having
On Monday, May 5, 2014 5:32:28 PM UTC-7, William wrote:
>
> On Mon, May 5, 2014 at 5:07 PM, John H Palmieri
> >
> wrote:
> >
> >
> > On Monday, May 5, 2014 4:41:39 PM UTC-7, William wrote:
> >>
> >> On Mon, May 5, 2014 at 4:16 PM, John H Palmieri
> >> wrote:
> >> >> -leif
> >> >>
> >>
I have not successfully built the Sage docs on my .5/1 GB (I forget which)
ram computer for quite some time. FWIW.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
t
On Mon, May 5, 2014 at 5:07 PM, John H Palmieri wrote:
>
>
> On Monday, May 5, 2014 4:41:39 PM UTC-7, William wrote:
>>
>> On Mon, May 5, 2014 at 4:16 PM, John H Palmieri
>> wrote:
>> >> -leif
>> >>
>> >> P.S.: If you haven't set MAKE, Sage "guesses" the number of threads to
>> >> use to build t
On Monday, May 5, 2014 4:41:39 PM UTC-7, William wrote:
>
> On Mon, May 5, 2014 at 4:16 PM, John H Palmieri
> >
> wrote:
> >> -leif
> >>
> >> P.S.: If you haven't set MAKE, Sage "guesses" the number of threads to
> >> use to build the Sage library as well as the docs, AFAIK.
> >
> >
> >
On Mon, May 5, 2014 at 4:16 PM, John H Palmieri wrote:
>> -leif
>>
>> P.S.: If you haven't set MAKE, Sage "guesses" the number of threads to
>> use to build the Sage library as well as the docs, AFAIK.
>
>
> Right: Sage uses SAGE_NUM_THREADS to decide how many threads to use for
> building spkgs
On Monday, May 5, 2014 3:53:17 PM UTC-7, leif wrote:
>
> On Tuesday, May 6, 2014 12:14:50 AM UTC+2, William wrote:
>
>> Hi,
>>
>> Does anybody know how much RAM is required to build Sage these days.
>> With MAKE not set, typing "make" with sage-6.2.rc2 on a VM with 4GB
>> RAM results in failu
On Tuesday, May 6, 2014 12:14:50 AM UTC+2, William wrote:
> Hi,
>
> Does anybody know how much RAM is required to build Sage these days.
> With MAKE not set, typing "make" with sage-6.2.rc2 on a VM with 4GB
> RAM results in failure (see below). Of course, I'm not using swap,
> and of course
I regularly build Sage on an old machine with 2Gb RAM without problems
(although I don't like running tests on it since it is single core). It has
swap (I think 2.5Gb, can't check right now), but it does not seem to be
used during compilation. However I saw that compiling/testing Sage requires
17 matches
Mail list logo
