Changes between Version 1 and Version 2 of JobTemplates

Timestamp:

Feb 15, 2013, 11:08:44 PM (12 years ago)

Author:

davea

Comment:

--

JobTemplates

@@ -48 +48 @@
   '''<sticky/>''':: if present, the file remains on the client after job is finished.
   '''<no_delete/>''':: if present, the file is not deleted from the server after job is completed.  Use this if the file is used as input to more than one job.
-  '''<report_on_rpc/>''':: if present, report file in each scheduler request (for sticky files)
-  '''<url>, <md5_cksum>, <nbytes>''':: used only for "non-local" input files (see below)
+  '''<report_on_rpc/>''':: if present, report file in each scheduler request (for sticky files).
+   Include this for compatibility with old (pre-7.x) clients; 7.0+ clients report all sticky files.
+  '''<url>, <md5_cksum>, <nbytes>''':: Use these for files that are [JobStage staged] to
+   a server (or servers) other than your BOINC server.
+   Each '''<url>''' element specifies a directory (i.e. it should end with a /) to which the file name will
+   be appended to give the URL.
+   You must provide the MD5 checksum and size of the file.
 
  '''<file_ref>''':: describes [BoincFiles#Filereferences the way the file is referenced].
@@ -68 +73 @@
    on a host with insufficient disk space.
 
-Notes:
- * The input template is copied into a BLOB column of the workunit table and will substitute filenames,
-  and have download urls, signatures and other elements inserted into your provided template.
-  The total expanded BLOB cannot exceed 65,535 bytes.
-  This is enough for about 200 input files,
-  fewer if you use long file names are multiple download URLs.
-  If this isn't enough, you can use [FileCompression BOINC file compression] to zip several files into a single file reference for download,
-  and expanding them prior to running on the client machine.
+The input template (substituted with filenames and URLs) is stored in a database field
+with a 64KB limit.
+This is enough for about 200 input files,
+fewer if you use long file names or multiple download URLs.
+If this isn't enough, you can use [FileCompression BOINC file compression] to zip several files into a single file reference for download,
+and expanding them prior to running on the client machine.
 
 == Output template files ==
@@ -143 +146 @@
 (i.e. no more replicas will be created).
 
-In general, you should not attempt to use more then 50 files in your output template.
-This is because the provided template will have upload URLs, and file names expanded, and signatures added to it.
-The total size of the result must remain under 65,535 bytes to fit in the xml_doc_in and xml_doc_out BLOBs in the result table.
-Your actual limit on number of files will depend upon the length of your job names, and upload URLs.
-If your expanded output template is approaching the size limit,
+The output template, substituted with filenames and URLs,
+is stored in a database field with a 64KB limit.
+This imposes a limit of about 50 output files;
+the exact number depends upon the length of your filenames and URLs.
+If you need more files,
 you can use [FileCompression BOINC file compression] to zip several files
 into a single file reference for upload, prior to completing each task on the client machine.
 Once you have run some jobs through your project,
-you can compare the size of the expanded xml with the 65,535 limit by running the following MySQL statement:[[BR]]
-{{{select max(length(xml_doc_in)), max(length(xml_doc_out)) from result;}}}[[BR]]
-Note that here "_in" and "_out" are both references to the output template.
-"_in" being when the task was created, and "_out" how it looked,
-with actual file sizes and checksums, at the time the task was returned.
-So don't confuse these column names with the "input" and "output" templates.
+you can compare the size of the expanded xml with the 65,535 limit by running the following MySQL statement:
+{{{
+select max(length(xml_doc_in)), max(length(xml_doc_out)) from result;
+}}}