Tags:
tag this topic
create new tag
view all tags
<!-- keep this as a security measure: * Set ALLOWTOPICCHANGE = Main.TWikiAdminGroup,Main.LCGAdminGroup * Set ALLOWTOPICRENAME = Main.TWikiAdminGroup,Main.LCGAdminGroup #uncomment this if you want the page only be viewable by the internal people #* Set ALLOWTOPICVIEW = Main.TWikiAdminGroup,Main.LCGAdminGroup --> KeyWords: SysAdmin, HostCe01, [[Torque]], [[News]], VoAtlas, VoCms, VoLhcb ---+ New job queue setup: queue by job duration, not by VO During yesterday's scheduled maintenance, a major change has been implemented for LHC VOs: jobs queues are now organized by duration, not by VO. The longest-running queue has the same limits that were formerly imposed on the VO-specific queues. The reason for this change was to allow jobs to use the cluster until the "last minute" when the cluster nodes are reserved for planned downtimes. The new queue setup requires proper specification of the job running time in the JDL file, otherwise your job may land in short time queue, and be killed before completion since it ran out of CPU time. Instructions on how to properly specify job duration requirements are given below. For more information, feel free to write an email to lcg@cscs.ch. ---++ The new queues The new queues have been given names that reflect the alloted CPU time (e.g., =egee8h= is for jobs using up to 8 hours of CPU time); the maximum wall-clock time has been computed by augmenting the CPU time by ~20%, with more leeway for shorter queues. (The rationale being that the excess wall-clock time is usually spent moving data to an SE; for shorter jobs, this will take a larger fraction of the total running time.) | *Queue* | *Max CPU Time* | *Max Wall-clock time* | | =egee1h= | 60 min (1 hour) | 90 min (1:30 hrs) | | =egee8h= | 480 min (8 hours) | 600 min (10 hours) | | =egee24h= | 1440 min (24 hours)| 1800 min (30 hours) | | =egee48h= | 2880 min (48 hours)| 3600 min (60 hours) | ---++ JDL requirements syntax In order to ensure that your job gets enough CPU or wall-clock time, a requirement must be stated using the =Requirements= attribute in the JDL file. To specify that a job needs _at least_ 120 minutes of CPU time, use the following line in your JDL file: <verbatim> Requirements = other.GlueCEPolicyMaxCPUTime > 120 </verbatim> To specify that a job needs _at least_ 180 minutes of wall-clock time, use the following line in your JDL file: <verbatim> Requirements = other.GlueCEPolicyMaxWallClockTime > 180 </verbatim> Requirements can be combined with the boolean =&&= (_and_) and =||= (_or_) operators, so you can also specify that a job needs at least 120 minutes of CPU time, _and_ 180 minutes of wall-clock time: <verbatim> Requirements = (other.GlueCEPolicyMaxCPUTime > 120) && (other.GlueCEPolicyMaxWallClockTime > 180) </verbatim> -- Main.RiccardoMurri - 30 Sep 2008
E
dit
|
A
ttach
|
Watch
|
P
rint version
|
H
istory
: r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r3 - 2011-01-21
-
PabloFernandez
LCGTier2
Log In
(Topic)
LCGTier2 Web
Create New Topic
Index
Search
Changes
Notifications
Statistics
Preferences
Users
Entry point / Contact
RoadMap
ATLAS Pages
CMS Pages
CMS User Howto
CHIPP CB
Outreach
Technical
Cluster details
Services
Hardware and OS
Tools & Tips
Monitoring
Logs
Maintenances
Meetings
Tests
Issues
Blog
Home
Site map
CmsTier3 web
LCGTier2 web
PhaseC web
Main web
Sandbox web
TWiki web
LCGTier2 Web
Users
Groups
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
P
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Warning: Can't find topic "".""
Account
Log In
E
dit
A
ttach
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback