New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sage is too big! #1293
Comments
comment:1
Well, your numbers are slighly inflated because "make install" is still experimental and copies fata not needed:
The current 2.8.13 binary expands to 802 MB which is still too large, but somewhat smaller than the 1.2GB you had. But it would be a good thing to slim down the installed Sage if it is possible. Cheers, Michael |
comment:2
Some numbers:
|
comment:3
Here are the brand new figures for sage-2.9 on a 64-bit computer (Opteron under Fedora7):
If the figures are comparable on sage.math (which I assume) this is 2.4 times larger than Mathematica and 3.9 times |
comment:4
Some new datapoints:
The result is 1.1GB which is still massive. I'm building with |
comment:5
I think this should also be safe in
to delete all autogenerated This seems to free ~ 80MB |
comment:6
Actually, the result is smaller than 1.1GB as I forgot to strip the Sage extensions. The result including the add-on above is 978M but still fully functional, I believe. |
comment:7
I guess this issue won't be fixed, thus I close this ticket. |
comment:8
Make sure you understand the procedure for closing tickets. See this section of the Developer's Guide for more information. |
comment:9
Sorry I didn't know I wasn't allowed to close tickets! |
I was told that SAGE did use less memory than Maple or Mathematica. I did check on sage.math.washington.edu:
I can understand that the SAGE developers need all the source and binaries installed, but I wish a minimal
version for the simple user that would use at most the same amount of memory than Maple or Mathematica,
not 2 times or 3 times more!
Component: distribution
Issue created by migration from https://trac.sagemath.org/ticket/1293
The text was updated successfully, but these errors were encountered: