On Oct 19, 9:09 am, kcrisman <kcris...@gmail.com> wrote: > Yes, let's keep in mind that notebook servers with fewer users are > usually very snappy and a great resource. It's not CPU power, but > number of simultaneous users, I think.
That suggests the bottleneck is disk I/O. Sage is quite large, so it's not a surprise. Anything you to slim down the software will make it "snappier" under load, and this is actually true at all levels of the memory hierarchy. Since Sage tries to be inclusive, you might try just slimming down the average case. How many libraries really need to be loaded at startup, etc? This is usually difficult to do. But for public servers it's unavoidable, and for software that runs in a "cloud", bloat = $$$. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
