[SciPy-Dev] sparsetools C++ code size

Ralf Gommers ralf.gommers at gmail.com
Sun Mar 9 15:03:26 EDT 2014


On Sat, Mar 8, 2014 at 9:14 PM, Pauli Virtanen <pav at iki.fi> wrote:

> 08.03.2014 19:22, Evgeni Burovski kirjoitti:
> [clip]
> > How bad is this at the moment? I mean, is it something we need to look
> > at before 0.15, or is it a blocker for 0.14 release? And if the latter
> > is the case, is there an urgent need for an alternative build machine
> > (not that I have one handy, but at least I can ask around if that'd
> > help)
>
> Here's a fix (reduces memory usage to half):
>
>     https://github.com/scipy/scipy/pull/3440
>
> I'm not sure if it's a blocker (except maybe in the practical sense that
> Ralf would have to get more memory), as the memory req anyway has
> hovered around the 1 GB limit for some time.
>

Since it does solve the practical issue and seems to work very well, I'm
tempted to merge it now. If anyone wants to take a closer look first,
please comment here or on the PR.

Ralf



> However, it certainly shows that SWIG is not very nicely scalable. I
> also don't like that we have several MB of crazy autogenerated code
> checked in the VCS, so it would be good to get rid of this altogether.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20140309/2e1710ea/attachment.html>


More information about the SciPy-Dev mailing list