Hi folks, The Sage cluster consists of four similar computers:
* sage.math --- mainly for Sage development (128GB RAM, 24 cores) * geom.math --- mainly for geometry research (128GB RAM, 24 cores) * mod.math --- mainly for number theory research (128GB RAM, 24 cores) * boxen.math --- mainly virtual machines and web services (128GB RAM 24 cores) The machine sage.math is primarily for Sage development. Ideally, you should use that machine to develop code, upgrade/update packages, porting packages/code, reviewing/working on tickets, etc. If you have a long job to run on the Sage cluster, first consider whether your job is related to any of these goals. Some questions relating to using any of these machines include: * If the job would take days or weeks or longer, does it relate to number-theoretic computation? If so, then mod.math is the machine to use as its stated purpose is for number theory research, which also includes number-theoretic computation. * Does your job relate to geometry computation? If so, then geom.math is the machine to use, since that is its intended purpose. Most of the time, you shouldn't run long jobs on boxen.math because that is for web services. We want to minimize the downtime of the public notebook server, the Sage wiki server, the trac bug server, the Sage main website, and websites of other projects hosted on boxen.math. The machines geom.math and mod.math are mostly at 50% load or thereabout and with plenty of system resources for you to run very long jobs. Please consider using those machines before running long jobs on sage.math. Running a long job on the machine sage.math --- where the job can take days, weeks, or months --- can significantly affect the development, compilation, and doctesting of the Sage library. When you work on a ticket, whether that be developing code or reviewing other people's code, you can use sage.math to parallel doctest the Sage library with that new code using 8 or 10 threads. This should significantly reduce the development and doctesting time from about 3 to 6 hours with one thread, to about 30 minutes with 16 threads. At the moment, I have been having problems doctesting the whole Sage library after merging new tickets. Normally I would use 16 threads for release management. But in the last few weeks, the increase use of sage.math for non-development work and running very long jobs has prompted me to use 4 to 10 threads for parallel doctesting. Previously, doing a parallel doctest with 4 threads wouldn't result in any doctest failures, where the version of Sage is known to pass all doctests with 4 threads. But as more and more jobs are run for days and weeks or longer, parallel doctesting with 4 threads have resulted in many doctest failures due to system resource issues. These issues usually relate to the low amount of free RAM on sage.math. The sooner that your tickets and code get merged in Sage, the sooner that users get to use your code and be grateful to you for providing useful software. So before running any long jobs on sage.math, please consider whether your job can be run on any of the other machines. -- Regards Minh Van Nguyen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
