Re: [sage-devel] Can't build Sage with 2GB RAM anymore

2015-04-25 Thread Andrey Novoseltsev
Just want to thank everybody involved in resolution!

My reliable horse is now kicking again:

novoselt@zvlm:~/sage$ time nice ionice -c3 make testlong
...
--
All tests passed!
--
Total time for all tests: 24923.4 seconds
cpu time: 16676.2 seconds
cumulative wall time: 24316.8 seconds

real910m6.541s
user739m5.011s
sys36m41.738s

With ~15 tab open in Firefox, the machine was perfectly responsive during 
build and didn't seem to use swap, until the documentation build, as usual.

Thank you!
Andrey

-- 
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 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Can't build Sage with 2GB RAM anymore

2015-04-25 Thread Volker Braun
On Saturday, April 25, 2015 at 11:55:38 PM UTC-4, Andrey Novoseltsev wrote:

 With ~15 tab open in Firefox, the machine was perfectly responsive during 
 build and didn't seem to use swap, until the documentation build, as usual.


So while we are at it, here is cpu/mem usage for make doc with a single 
thread:

https://lh3.googleusercontent.com/-m_h3hpLftiA/VTxq4N6Mi8I/Vd4/xhHwbCf0B6g/s1600/make_doc_serial.png
You can clearly see the first pass (and the combinat docs at the beginning 
of it), then the second pass, and then the assorted small docs.

I guess the importing of the inventory in the second pass uses a bit over a 
gigabyte. Thats pretty steep...

And for fun, the parallel build (on my quad-core i7 laptop) where now the 
time for the first and second pass is set by the combinat docs:

https://lh3.googleusercontent.com/-8cvpf2hyck8/VTxrnennyQI/VeA/nSCQlWTcDz8/s1600/make_doc_parallel.png



-- 
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 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Can't build Sage with 2GB RAM anymore

2015-04-24 Thread Jeroen Demeyer
Upstream Cython has now fixed this and I made a new Cython package for 
Sage with this patch. Please review


http://trac.sagemath.org/ticket/18294

--
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 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Can't build Sage with 2GB RAM anymore

2015-04-24 Thread Jeroen Demeyer

Sage ticket: http://trac.sagemath.org/ticket/18294

--
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 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Can't build Sage with 2GB RAM anymore

2015-04-20 Thread Clemens Heuberger

I have a somewhat related problem: Since February (I do not recall the exact
revision, but might very well be early in the 6.6 release cycle), I cannot do a
parallel build with 4 processes on my notebook with 4 GB RAM anymore.

My observation was that cythonizing takes huge amounts of memory (~ 2 GB) per
process. Interrupting it and typing make again reduced the maximum memory usage.

I then tried to somehow compare that with 6.5 and tried to limit my memory with
ulimit; but also then, cythonizing took lots of memory. I then stopped
investigating this and resigned myself to parallel builds with two processes.

Regards, CH

Am 2015-04-20 um 19:10 schrieb Thierry:
 Hi,
 
 i confirm i had the same issue on a Genuine Intel(R) CPU T2050 @ 1.60GHz
 with 1GB of RAM (+1.5GB swap), the build of 6.5 was sucessful, but get stuck 
 for
 6.6.
 
 Ciao,
 Thierry
 
 
 
 On Mon, Apr 20, 2015 at 09:33:24AM -0700, Andrey Novoseltsev wrote:
 Hello,

 Up to Sage-6.5 I was able to build it on my old laptop with 2GB RAM. It has 
 swap as well, but I don't think it was used much, the wall time was just a 
 bit bigger than user+system, about 8-9 hours.

 With Sage-6.6 it gets stuck while processing rings directory: swap is not 
 full yet, but it seems that necessary stuff does not fit RAM anymore - 
 heavy disk usage, low CPU temperature, not much progress after more than a 
 day, top was showing python setup.py if I recall correctly consuming 
 1.5GB RAM and over 2.5GB virtual memory. This consistent over several 
 attempts with make distclean, with nothing running apart from MATE 
 session and a terminal window.

 I realize that supporting builds on such computers may not be a high 
 priority, if at all, but perhaps it is a manifestation of some bug.

 Besides, while 2GB total RAM seems small nowadays, 2GB/core is quite 
 common, especially with VMs. (In fact, all physical and virtual machines 
 that I use frequently happen to have exactly this number, ranging from 
 2GB/1 core to 32GB/16 cores.)

 Thank you,
 Andrey

 -- 
 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 to sage-devel+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-devel@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-devel.
 For more options, visit https://groups.google.com/d/optout.
 


-- 
Univ.-Prof. Dr. Clemens HeubergerAlpen-Adria-Universität Klagenfurt
Institut für Mathematik, Universitätsstraße 65-67, 9020 Klagenfurt, Austria
Tel: +43 463 2700 3121Fax: +43 463 2700 99 3121
clemens.heuber...@aau.athttp://wwwu.aau.at/cheuberg

-- 
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 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Can't build Sage with 2GB RAM anymore

2015-04-20 Thread Thierry
Hi,

i confirm i had the same issue on a Genuine Intel(R) CPU T2050 @ 1.60GHz
with 1GB of RAM (+1.5GB swap), the build of 6.5 was sucessful, but get stuck for
6.6.

Ciao,
Thierry



On Mon, Apr 20, 2015 at 09:33:24AM -0700, Andrey Novoseltsev wrote:
 Hello,
 
 Up to Sage-6.5 I was able to build it on my old laptop with 2GB RAM. It has 
 swap as well, but I don't think it was used much, the wall time was just a 
 bit bigger than user+system, about 8-9 hours.
 
 With Sage-6.6 it gets stuck while processing rings directory: swap is not 
 full yet, but it seems that necessary stuff does not fit RAM anymore - 
 heavy disk usage, low CPU temperature, not much progress after more than a 
 day, top was showing python setup.py if I recall correctly consuming 
 1.5GB RAM and over 2.5GB virtual memory. This consistent over several 
 attempts with make distclean, with nothing running apart from MATE 
 session and a terminal window.
 
 I realize that supporting builds on such computers may not be a high 
 priority, if at all, but perhaps it is a manifestation of some bug.
 
 Besides, while 2GB total RAM seems small nowadays, 2GB/core is quite 
 common, especially with VMs. (In fact, all physical and virtual machines 
 that I use frequently happen to have exactly this number, ranging from 
 2GB/1 core to 32GB/16 cores.)
 
 Thank you,
 Andrey
 
 -- 
 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 to sage-devel+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-devel@googlegroups.com.
 Visit this group at http://groups.google.com/group/sage-devel.
 For more options, visit https://groups.google.com/d/optout.

-- 
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 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Can't build Sage with 2GB RAM anymore

2015-04-20 Thread Andrey Novoseltsev
Hello,

Up to Sage-6.5 I was able to build it on my old laptop with 2GB RAM. It has 
swap as well, but I don't think it was used much, the wall time was just a 
bit bigger than user+system, about 8-9 hours.

With Sage-6.6 it gets stuck while processing rings directory: swap is not 
full yet, but it seems that necessary stuff does not fit RAM anymore - 
heavy disk usage, low CPU temperature, not much progress after more than a 
day, top was showing python setup.py if I recall correctly consuming 
1.5GB RAM and over 2.5GB virtual memory. This consistent over several 
attempts with make distclean, with nothing running apart from MATE 
session and a terminal window.

I realize that supporting builds on such computers may not be a high 
priority, if at all, but perhaps it is a manifestation of some bug.

Besides, while 2GB total RAM seems small nowadays, 2GB/core is quite 
common, especially with VMs. (In fact, all physical and virtual machines 
that I use frequently happen to have exactly this number, ranging from 
2GB/1 core to 32GB/16 cores.)

Thank you,
Andrey

-- 
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 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.