| ... | ... | @@ -211,7 +211,7 @@ Check out the [dedicated section](https://compss-doc.readthedocs.io/en/latest/Se |
|
|
|
|
|
|
|
EARL loading is **only available** using `enqueue_compss` and with Python applications.
|
|
|
|
The command has the flag `--ear` which you can set either a boolean (i.e., *true* or *false*) or a string value.
|
|
|
|
The latter can be any of the [job submission flags](ear-job-submission-flags).
|
|
|
|
The latter can be any of the [job submission flags](#ear-job-submission-flags).
|
|
|
|
See the [example](https://compss-doc.readthedocs.io/en/latest/Sections/05_Tools/05_EAR.html#example) provided by the COMPSs documentation.
|
|
|
|
|
|
|
|
# Retrieving EAR data
|
| ... | ... | @@ -223,7 +223,7 @@ kind of information. |
|
|
|
|
|
|
|
As a very simple hint of your application workload, you can enable EARL verbosity (i.e., `--ear-verbose=1`) to get loop data at runtime.
|
|
|
|
**The information is shown at _stderr_ by default.**
|
|
|
|
Read how to set up verbosity at [submission time](ear-job-submission-flags) and
|
|
|
|
Read how to set up verbosity at [submission time](#ear-job-submission-flags) and
|
|
|
|
[verbosity environment variables](EAR-environment-variables#verbosity) provided
|
|
|
|
for a more advanced tunning of this EAR feature.
|
|
|
|
|
| ... | ... | |