
The following is my suggested text for the MemoryLimit and PipeSizeLimit element definitions. The text in [brackets] is non-normative. I have omitted the text stating what it must be a sub-element of (according to the principles of allowing the schema to be used as an ontology as well as a document definition) but if we really want that, it's trivial to add it. MemoryLimit: Definition This element is a positive integer that describes the maximum amount of physical memory (in bytes) that the job should use when executing. It MUST be supported. If this is not present, then it is unlimited. [This is really the Resident Set Size limit, and systems might impose a granularity of a kilobyte.] PipeSizeLimit: Definition This element is a positive integer that describes the maximum size of pipelines (in bytes) created for and by the processing of the job. It MUST be supported. If this is not present, then the system should use its default value. [No system permits arbitrary sized pipe buffers, but their defaults are usually entirely acceptable. Systems typically impose a granularity of 512 bytes.] Donal.
participants (1)
-
Donal K. Fellows