On Tue, 15 Nov 2011 at 07:59PM -0800, William Stein wrote: > To build, I had to install these packages: > > yum install gcc emacs make screen gcc-c++ gcc-gfortran
You need emacs to build Sage? Wow, emacs really *is* an operating system...! > The build literally took *4 DAYS* to complete (!). However, > everything built fine with no problems. I hope it took so long due > to swap being slow, and not Amazon's EC2's being really slow, but I > don't know. The EC2 virtual disks seem fast -- startup time is very > good, for example and compute benchmarks like "factorial(10^7)" are > basically the same on sage.math as EC2. I'm guessing the build would > be a lot faster with a non-free EC2 virtual machine that has more RAM. I recall that the Amazon guy who built Sage on EC2 used a much more powerful node and got it to build in 70 minutes or so. I think it's just your swap file. But that's just my guess. > I have not been able to get the notebook server to work at all yet > though, perhaps due to some firewalling by Amazon that I haven't > figured out how to disable yet. That would be *great* if we can run a notebook server on EC2. Even the current notebook would be useful. You have a class, start it up, spend a few bucks, and let it sit idle until you need it again. Long-term, being able to separate the webserver node from compute nodes will make that even more efficient and scalable. Yay! Dan -- --- Dan Drake ----- http://mathsci.kaist.ac.kr/~drake -------
signature.asc
Description: Digital signature