Is there any difference between the following (e.g. performance-wise):
$ make && cp bin/myexecutable inputfile.txt $workdir && cd $workdir $ <series of sed commands to modify inputfile.txt> $ mpirun -n 12 ./myexecutable [args]
versus doing it via a script:
#!/bin/bash make && cp bin/myexecutable inputfile.txt $workdir && cd $workdir <series of sed commands to modify inputfile.txt> mpirun -n 12 ./myexecutable [args]
The reason for asking is that I often run multiple (10-100 or more) simulation jobs on a workstation. Each job will run in a different working directory (and have a different input file, with a different set of parameters)--so scripting the runs will make it easier to run many tests over a large set of parameters. Some of the simulation runs could be over several days.
Would the difference in performance be negligible (i.e. < 5-10%)? Could the script (vs the command line) see a different environment and therefore cause something to go wrong?