a huge number of small tasks - a lot of time is spent downloading input files

while both input files are the same for this version of the application or at least the current series of tasks (batch)
you can significantly reduce the load on the server if you mark these files with the "sticky" tag in the WU template

<input_template>
    <file_info>
    . . . . . .
         <sticky/> 
         <no_delete/> 
    </file_info>

    <workunit>
    . . . . . .
    </workunit>
</input_template>

<sticky/> if present, the file remains on the client after job is finished.
<no_delete/> if present, the file is not deleted from the server after job is completed. Use this if the file is used as input to more than one job.

the option is possible -
constant config for the application version,
input data are constant for a series of tasks, a specific batch, etc.

Yes please!

And unless these are just test tasks to see if the server will hold up under load, please make longer tasks.

Thank you for the information. Please be patient . These are test tasks for server ...

I did 'only' 114 tasks on 1 PC so far and have already loaded 13GB Gaia-project data.
Only 3.5GB left for BOINC and I can't extend the space or move the data.
Since bin-files are not purged after the job, I've to reset the project regulary.

I used option </nodelete> for limiting transfer, but problem with space.
So, I am thinking of a compromise ....