mirror of
https://git.savannah.gnu.org/git/parallel.git
synced 2024-12-22 20:57:53 +00:00
parallel.pod: Batch jobqueue processor.
This commit is contained in:
parent
d847c932f5
commit
cd9efa9ab8
|
@ -171,9 +171,9 @@ cc:Sandro Cazzaniga <kharec@mandriva.org>,
|
|||
Ryoichiro Suzuki <ryoichiro.suzuki@gmail.com>,
|
||||
Jesse Alama <jesse.alama@gmail.com>
|
||||
|
||||
Subject: GNU Parallel 20130122 ('') released
|
||||
Subject: GNU Parallel 20130122 ('Jyoti Singh Pandey') released
|
||||
|
||||
GNU Parallel 20130122 ('') has been released. It is
|
||||
GNU Parallel 20130122 ('Jyoti Singh Pandey') has been released. It is
|
||||
available for download at: http://ftp.gnu.org/gnu/parallel/
|
||||
|
||||
New in this release:
|
||||
|
|
|
@ -2411,17 +2411,23 @@ system/batch manager:
|
|||
|
||||
=item *
|
||||
|
||||
You will get a warning if you do not submit JobSlots jobs within the
|
||||
first second. E.g. if you have 8 cores and use B<-j+2> you have to submit
|
||||
10 jobs. These can be dummy jobs (e.g. B<echo foo>). You can also simply
|
||||
ignore the warning.
|
||||
You will get a warning if you do not submit JobSlots jobs within
|
||||
the first second. E.g. if you have 8 cores and use -j+2 you have to
|
||||
submit 10 jobs. These can be dummy jobs (e.g. echo foo). You can also
|
||||
simply ignore the warning. For parallel versions 20110322 and higher,
|
||||
the warnings will not appear.
|
||||
|
||||
=item *
|
||||
|
||||
Jobs will be run immediately, but output from jobs will only be
|
||||
printed when JobSlots more jobs has been started. E.g. if you have 10
|
||||
jobslots then the output from the first completed job will only be
|
||||
printed when job 11 is started.
|
||||
You have to submit JobSlot number of jobs before they will start, and
|
||||
after that you can submit one at a time, and job will start
|
||||
immediately if free slots are available. Output from the running or
|
||||
completed jobs are held back and will only be printed when JobSlots
|
||||
more jobs has been started (unless you use --ungroup or -u, in which
|
||||
case the output from the jobs are printed immediately). E.g. if you
|
||||
have 10 jobslots then the output from the first completed job will
|
||||
only be printed when job 11 has started, and the output of second
|
||||
completed job will only be printed when job 12 has started.
|
||||
|
||||
=back
|
||||
|
||||
|
@ -2438,9 +2444,6 @@ B<inotifywait -q -m -r -e MOVED_TO -e CLOSE_WRITE --format %w%f my_dir | paralle
|
|||
This will run the command B<echo> on each file put into B<my_dir> or
|
||||
subdirs of B<my_dir>.
|
||||
|
||||
The B<-u> is needed because of a small bug in GNU B<parallel>. If that
|
||||
proves to be a problem, file a bug report.
|
||||
|
||||
You can of course use B<-S> to distribute the jobs to remote
|
||||
computers:
|
||||
|
||||
|
@ -2451,6 +2454,9 @@ If the files to be processed are in a tar file then unpacking one file
|
|||
and processing it immediately may be faster than first unpacking all
|
||||
files. Set up the dir processor as above and unpack into the dir.
|
||||
|
||||
Using GNU Parallel as dir processor has the same limitations as using
|
||||
GNU Parallel as queue system/batch manager.
|
||||
|
||||
|
||||
=head1 QUOTING
|
||||
|
||||
|
|
Loading…
Reference in a new issue