Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Slurm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tud-zih-energy
Slurm
Commits
3aa77cab
Commit
3aa77cab
authored
14 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
note peak job submit rate.
parent
d1dc4a72
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/html/high_throughput.shtml
+5
-3
5 additions, 3 deletions
doc/html/high_throughput.shtml
with
5 additions
and
3 deletions
doc/html/high_throughput.shtml
+
5
−
3
View file @
3aa77cab
...
@@ -11,8 +11,9 @@ for this material.</p>
...
@@ -11,8 +11,9 @@ for this material.</p>
<h2>Performance Results</h2>
<h2>Performance Results</h2>
<p>SLURM has been validated to execute 32,000 jobs per hour on a
<p>SLURM has been validated to accept 1,000 job creations in under 10 seconds
sustained basis (about 9 jobs per second).</p>
and to fully execute those jobs in 16 seconds. Actual performance depends upon
the jobs to be executed plus the hardware and configuration used.</p>
<h2>System configuration</h2>
<h2>System configuration</h2>
...
@@ -74,7 +75,8 @@ seconds if possible.</li>
...
@@ -74,7 +75,8 @@ seconds if possible.</li>
It is desirable to configure the <b>slurmctld</b> daemon to accept incoming
It is desirable to configure the <b>slurmctld</b> daemon to accept incoming
messages on more than one port in order to avoid having incoming messages
messages on more than one port in order to avoid having incoming messages
discarded by the operating system due to exceeding the SOMAXCONN limit
discarded by the operating system due to exceeding the SOMAXCONN limit
described above.</li>
described above. Using between two and ten ports is suggested when large
numbers of simultaneous requests are to be supported.</li>
<li>Other: Configure logging, accounting and other overhead to a minimum
<li>Other: Configure logging, accounting and other overhead to a minimum
appropriate for your environment.</li>
appropriate for your environment.</li>
</ul>
</ul>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment