computing_drop
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
computing_drop [2009/04/24 10:06] – leeuwen | computing_drop [2009/05/06 17:37] (current) – leeuwen | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== DROP cluster ==== | + | ====== DROP cluster |
*Drop is: | *Drop is: | ||
- | | + | * drop.astron.nl |
- | + | * With 6 nodes at 8 cores each, DROP is designed for non-interactive queue-based parallel supercomputing. | |
- | * Drop is not: | + | *Drop is not: |
- | | + | |
- | than 8 parallel cores per job, is not queue-able, or generally takes | + | |
- | less than a few nights to run on your desktop, you had better use one | + | |
- | of the stand-alone servers. | + | |
| | ||
| | ||
+ | | ||
+ | |||
+ | *Come see Joeri for an account | ||
+ | |||
+ | *File systems | ||
+ | */ | ||
+ | *RAID6, 20GB/user quota, nothing ever auto-deleted | ||
+ | */data (crossmounted over all nodes) = RAID0, unlimited space | ||
+ | *RAID0, 5TB, no quotas | ||
+ | *heaviest users will have older data auto-deleted by semi-random script, so better clear it out yourself | ||
+ | |||
+ | * Login/ | ||
+ | * Queueing implemented to balance loads. Only use queue, do not start processing on your own. | ||
+ | * Cluster runs [[http:// | ||
- | * Come see Joeri for an account | ||
- | * File systems | ||
- | * / | ||
- | * RAID6, 20GB/user quota | ||
- | * /data (crossmounted over all nodes) = RAID0, unlimited space | ||
- | * RAID0, 5TB, no quotas | ||
- | * heaviest users will have older data auto-deleted by semi-random script, so better clear it out yourself |
computing_drop.1240567600.txt.gz · Last modified: 2009/04/24 10:06 by leeuwen