Changes between Version 8 and Version 9 of JobSubmission

Timestamp:

Mar 7, 2010, 2:05:01 PM (15 years ago)

Author:

feet1st

Comment:

Added details about file template 64K size limit

JobSubmission

@@ -78 +78 @@
    on a host with insufficient disk space.
 
+Note: 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. As a general rule, you should plan to use less then 15 files in your input template. This will allow you some flexibility on making your job names longer, adding more options to your command line, or adding additional download servers as your project grows. If you require more then 15 application and input files, you can achieve this using [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. You can check to see how large your expanded input templates become by comparing 65,535 with the output the following MySQL statement:[[BR]]
+{{{select max(length(xml_doc)) from workunit;}}}
+
 == Output template files ==
 
@@ -132 +135 @@
 If this is not desired, you must create a new output template file.
 
-You can safely remove a workunit template file after creating your last WU with it.
-However, you can't delete a result template file until any WU that refers to it is completed
+You can safely remove an input template file after creating your last job with it.
+However, output template files must exist until any task that refers to it is completed
 (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, 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.
 
 == Staging input files ==