Changes between Version 12 and Version 13 of JobIn

Timestamp:

Jul 13, 2011, 3:23:56 PM (13 years ago)

Author:

davea

Comment:

--

JobIn

@@ -26 +26 @@
 === Resource estimates and bounds === #resources
 
+It's important that you supply accurate values for these parameters.
+See [JobEst estimating job sizes] for tips on how to do so.
+
  '''rsc_fpops_est'''::
-        An estimate of the average number of floating-point operations required to complete the computation. This is used to estimate how long the computation will take on a given host.
+        An estimate of the number of floating-point operations required to complete the job, used to estimate how long the job will take on a given host.
  '''rsc_fpops_bound'''::
-        A bound on the number of floating-point operations required to complete the computation. If this bound is exceeded, the application will be aborted.
+        An upper bound on the number of floating-point operations required to complete the job. If this bound is exceeded, the job will be aborted.
  '''rsc_memory_bound'''::
-        An estimate of application's largest working set size. The workunit will only be sent to hosts with at least this much available RAM.
+        An estimate of job's largest working set size. The job will only be sent to hosts with at least this much available RAM.  If this bound is exceeded, the job will be aborted.
  '''rsc_disk_bound'''::
-        A bound on the maximum disk space used by the application, including all input, temporary, and output files. The workunit will only be sent to hosts with at least this much available disk space. If this bound is exceeded, the application will be aborted.
+        A bound on the maximum disk space used by the job, including all input, temporary, and output files. The job will only be sent to hosts with at least this much available disk space. If this bound is exceeded, the job will be aborted.
  '''rsc_bandwidth_bound'''::
-  If nonzero, this job will be sent only to hosts with at least this much download bandwidth.  Use for applications with very large input files.
-
-It's important that you supply accurate values for these parameters. To get initial estimates, run your application on your own machines, and monitor the memory and disk usage. To view the distribution of FLOPs, use the script html/ops/job_times.php (the '''FLOP count statistics''' link on your project's [HtmlOps administrative web interface]).
+  If nonzero, this job will be sent only to hosts with at least this much download bandwidth.  Use for jobs with very large input files.
 
 === Redundancy and scheduling attributes === #scheduling