Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 677043 Details for
Bug 892804
Update Chapter 17 to outline how resources are now divided.
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
[patch]
Documentation update for how resources are split
DSlots.patch (text/plain), 2.05 KB, created by
Timothy St. Clair
on 2013-01-11 18:28:09 UTC
(
hide
)
Description:
Documentation update for how resources are split
Filename:
MIME Type:
Creator:
Timothy St. Clair
Created:
2013-01-11 18:28:09 UTC
Size:
2.05 KB
patch
obsolete
>Index: en-US/Dynamic_Slots.xml >=================================================================== >--- en-US/Dynamic_Slots.xml (revision 88028) >+++ en-US/Dynamic_Slots.xml (working copy) >@@ -250,5 +250,30 @@ > request_actuator = 1 > </programlisting> > </example> >+ >+ <example id="exam-Grid_User_Guide-Dynamic_slots-Configuring_resource_partioning_sizes"> >+ <title>Configuring resource partitioning sizes</title> >+ <para> >+ Once the job has been matched, and has made it to the execute machine, the condor_startd has the ability to modify these resource requests before using them to size the actual dynamic slots carved out of the partitionable slot. >+ Clearly, for the job to work, the condor_startd daemon must create slots with at least as many resources as the job needs. >+ However, it may be valuable to create dynamic slots somewhat bigger than the job's request, as subsequent jobs may be more likely to reuse the newly created slot when the initial job is done using it. >+ </para> >+ <para> >+ The condor_startd configuration variables which control this and their defaults are: >+ </para> >+ >+<programlisting> >+MODIFY_REQUEST_EXPR_REQUESTCPUS = quantize(RequestCpus, {1}) >+MODIFY_REQUEST_EXPR_REQUESTMEMORY = quantize(RequestMemory, {256}) >+MODIFY_REQUEST_EXPR_REQUESTDISK = quantize(RequestDisk, {1024}) >+</programlisting> >+ <para> >+ The modify expressions use the quantize function which partitions to the the largest multiple greater then the request. >+ Therefore, in the case where a user were to set <command>RequestMemory=300</command> the dynamic slot created will have <command>SlotMemory=512</command>. >+ If the user desires legacy behavior they can set <command>MODIFY_REQUEST_EXPR_MEMORY=RequestMemory</command>, or likewise for the other attributes. >+ </para> >+ >+ </example> >+ > </chapter>
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 892804
: 677043