On 04/26/2015 06:39 AM, Volker Braun wrote:
> 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.
On 04/23/2015 03:36 AM, Volker Braun wrote:
> I wouldn't want another environment variable for that.
Well, easier for playing than editing the sources... ;-)
A good default value should be chosen automatically.
> If we have to,
> chunking at 10 would be fine.
I think it's ok for machines with 2
PS: The script for plotting cpu/mem usage is now at
https://github.com/vbraun/GraphPG
--
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...@goog
I wouldn't want another environment variable for that. If we have to,
chunking at 10 would be fine. Though ideally this would be dealt with on
the cython side, I made a post here:
https://groups.google.com/d/msg/cython-users/7UoMj84Y5os/6UAXi64MA88J
On Wednesday, April 22, 2015 at 6:04:41 PM U
On 04/21/2015 11:57 PM, Andrey Novoseltsev wrote:
> It is a single core single thread 64-bit CPU (Athlon 64M), suggestions
> to use USB 3/PCIe SSD are funny but miss the point: for no apparent gain
> systems that were capable of building Sage can't do it anymore (or
> require tweaking to reduce par
On 04/22/2015 02:05 PM, Volker Braun wrote:
> On Wednesday, April 22, 2015 at 12:07:53 AM UTC-4, leif wrote:
>
> Hmmm, I also tried that yesterday (with SAGE_NUM_THREADS=8) but none of
> the python processes was consuming more than 1 GB (in fact less)
>
>
> Same here. That is because 5gb
On Wednesday, April 22, 2015 at 12:07:53 AM UTC-4, leif wrote:
>
> Hmmm, I also tried that yesterday (with SAGE_NUM_THREADS=8) but none of
> the python processes was consuming more than 1 GB (in fact less)
Same here. That is because 5gb / 8 < 1gb. But I'm pretty sure if you had
only one process
On 04/22/2015 05:01 AM, Volker Braun wrote:
> It seems that Cython is now cythonizing multiple files in a single
> process, that is, the Cython process does not quit while cythonizing the
> entire Sage library. Combined with a small memory leak in Cython means
> that you currently need about 5gb of
It seems that Cython is now cythonizing multiple files in a single process,
that is, the Cython process does not quit while cythonizing the entire Sage
library. Combined with a small memory leak in Cython means that you
currently need about 5gb of ram.
For example, in the attached plot I recor
Here is the tail of the typical terminal output:
...
warning: sage/rings/finite_rings/element_givaro.pyx:1105:39: local variable
'r' referenced before assignment
warning: sage/rings/finite_rings/element_givaro.pyx:1120:50: local variable
'r' referenced before assignment
warning: sage/rings/finit
On 04/21/2015 11:35 AM, Thierry wrote:
> could this mean that there is some issue with Cython compilation (e.g.
> memory leak) ?
Not necessarily a leak, but Cython 0.22 sneaked into Sage 6.6.beta0, in
February. (Leaks usually just increase the amount of virtual memory
used, not the number of page
Hi,
could this mean that there is some issue with Cython compilation (e.g.
memory leak) ?
Ciao,
Thierry
On Tue, Apr 21, 2015 at 10:24:07AM +0200, leif wrote:
> On 04/21/2015 08:27 AM, Simon King wrote:
> > On 2015-04-21, Clemens Heuberger wrote:
> >> I have a somewhat related problem: Since Fe
On 04/21/2015 08:27 AM, Simon King wrote:
> On 2015-04-21, Clemens Heuberger wrote:
>> 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 notebo
Hi!
On 2015-04-21, Clemens Heuberger wrote:
> 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.
For a similar re
Hi Andrey
I can confirm that sage-6.6 was built successfully on an 8 year old pentium
with 2GB of RAM and about 10 GB of swap, I was looking from time to time at
the swap use during the ~15 hours built, I think almost 3GB was the top.
This was done with Debian Jessie, which I have to say, is th
On 04/20/2015 06:33 PM, Andrey Novoseltsev wrote:
> 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.
I hope the 8-9 hours refer to the total time,
On Monday, 20 April 2015 12:10:21 UTC-6, Volker Braun wrote:
>
> Which build step / which setup.py? Logs?
>
I believe it was building Sage itself and getting stuck at rings. Can't
provide a log now, will try to run it again overnight and post a log
tomorrow.
>
> On Monday, April 20, 2015 at
Which build step / which setup.py? Logs?
On Monday, April 20, 2015 at 12:33:24 PM UTC-4, 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
18 matches
Mail list logo
