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 ram. > > For example, in the attached plot I recorded cpu load (red) and total > memory usage (rss, blue) for "sage -ba" on my quad-core i7 laptop. > During the cythonize phase the memory usage grows continuously while the > 8 Cython processes work through the Sage library.
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), but probably the machine was too fast for me... At least the Cython release notes for 0.22 don't contain anything suspicious. Even if the data of all files would be kept until the process exits, I don't see why that should cause thrashing; most pages should be dead after a while, unless Cython used extremely poor data structures. I'll retry with more verbose 'time' output on a machine with just 2 GB the next days. -leif -- 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.
