Differences

This shows you the differences between two versions of the page.

--- condor [2016/01/12 12:37]
aykutbulut [Using AMPL with Condor]
+++ condor [2017/07/16 00:05] (current)
sertalpbilal [CONDOR]
@@ Line 1: / Line 1: @@
 ======CONDOR======
+<note warning>This page is about our retired job scheduling system **CONDOR**. Check [[tutorial:torque|Torque]] to schedule jobs in Polyps.</note>
 ===== What is CONDOR =====
@@ Line 261: / Line 264: @@
 ===== Some other CONDOR commands =====
-^ Command ^ Action ^
+^ Command ^ Action ^ Info ^
 | ''condor_userprio'' | shows the user priority | condor_userprio |
 | ''condor_status'' | show the current status of CONDOR nodes |
@@ Line 277: / Line 280: @@
 ''concurrency_limits = AMPL''
+===== Condor Jobs Memory Usage =====
+Please check status of your condor jobs regularly, especially memory usage.
+Each polyp node has 16 processors and 32 GB memory. This means 1 process
+gets 2 GB memory in average.
+When a polyp node is out of memory it starts using hard drive (swap) as memory
+but reading and writing from hard drives is 1000 times slower. This means
+if your jobs are using large amounts of memory and the polyp node processing
+your job is out of memory, do not expect your job to terminate.
+Tips:
+You can see memory usage of your job using ''condor_q'' command (7th column
+gives memory usage in MB).
+You can check the node your job is running using ''condor_q -run''
+You can check memory status in a node using ''ssh polyp6 "vmstat -s"''.
+For more memory checking commands see http://www.binarytides.com/linux-command-check-memory-usage/
+or google is your friend.
+**Your job might get killed if it is using swap. Do not waste your
+system administrators' time with this and force them to police the condor jobs.
+Just control your jobs and submit jobs that are reasonable.**

Lehigh ISE / COR@L Lab Wiki

User Tools

Site Tools

Differences

Page Tools