On 09/01/2012 08:23 PM, Keshav Kini wrote:
David Kirkby<[email protected]>  writes:
On 31 August 2012 21:20, Guilherme Boaviagem Ribeiro
<[email protected]>  wrote:
Hi everyone,

I have installed Sage (with the file sage-5.0-disk1.vmdk) on my Windows
64-bits (4 GB RAM, and processor of 2.4 GHz), and it is already running in
my Virtual Box. But it's way too slow, even for the simplest commands, does
anyone have any idea of what could be the reason for this? My virtual
machine is running Sage in Fedora with 512 MB of memory and 16 MB of video
memory.

512 MB of RAM seems far too low to me. As someone else pointed out,
Sage is not a small program. Personally I'd look at the possibility of
shrinking the Windows partition a bit, and dual-booting with Linux.
Then you will have the full 4 GB for Sage.

I found the best way to shrink the Windows partition under Windows
Vista was to get a trial of a 3rd party parition tool. I forget what
it is, but it could defragment the disk far more than Windows could.
You also need to disable the hybernation mode temporarily, and turn
off the ability to page to disk. If you do both of them, you should be
able to shrink the partition, then install Linux.

Honestly I don't think it's very constructive to tell users that they
should install a different operating system in order to use Sage, and
that is basically what this dual-booting suggestion amounts to -
dual-booting is unlikely to be a very convenient way for anyone to use
Sage unless they start using the Sage-capable OS for their other
programs as well. The ability to multitask is something that everyone
assumes these days. I doubt many people are willing to reboot their
computer and do nothing but type code in Sage for a stretch of time,
then reboot again and do everything other than Sage for a stretch of
time. This doesn't make sense.

-Keshav


That's quite true. The OP should try a couple of things that have already been mentioned:

1. enable VT-x if your processor supports it. Sometimes, virtualization support is also turned off in the BIOS and needs to be enabled there.

2. Increase the VM memory to, say 2G or 2.5G. If your windows is windows 7, it should run just fine in the remaining about 1G+ of memory, as long as you don't open other heavy programs.

3. Increase the number of processors, say from 1 to 2, allocated to the VM.

--
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
Visit this group at http://groups.google.com/group/sage-support?hl=en.


Reply via email to