On Dec 9, 2007 6:57 PM, M. Edward (Ed) Borasky <[EMAIL PROTECTED]> wrote: > root wrote: > >> The main plus of this packaging for sage is that it builds from > >> source quickly (in a few minutes) using precompiled clisp files. > > > > Well, on my 2Ghz machine with 2 Gig of memory running VMWare and > > using the sage vmware image (but upgrading the VM to have 1G memory) > > I started the package-install at 3:30am this morning. It is now > > 2:10pm and the build is still "in-process". They are heavy things, > > your minutes :-) > > UH ... before we go hunting for Fricas performance issues in the build, > let's make sure we aren't experiencing a VMware performance issue. :) > > 1. What version of VMware are you running?
It's likely the latest vmware player for windows > 2. Is the/are the virtual disk(s) de-fragmented? Yes, definitely. I do that every time right before creating the vmware image. > 3. What's your host, and what does your host's "native" performance > monitor tool (Task Manager on Windows or "top" on Linux) show the > virtual machine is doing? You'll see a process at the top of the list > named something like "vmware-vmx". That would be interesting. All that said, Tim's guess that the problem is doing the install through the sage notebook instead of using the command line directly is a good guess. Tim, any chance you could try doing: login: manage $ sudo su password: sage $ sage -f fricas-0.3.1 and see how long it takes? This will let us know if the problem is more vmware-related or something that can be fixed by changing the notebook's behavior somewhat. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
