[Enhancement] Enhancmeent for zos_operator to consider adopting shorter increments than a second

For the singly-threaded Ansible automation, introducing such an option would have little impact because the overhead to form and close the SSH connection between the controller and the managed node would take much longer than the fractional seconds saved by allowing for smaller units of wait_time_s.

Where things could get interesting is if there is a multi-threaded approach, where the overhead overlaps each other, so even though each 'operation' takes second(s) to form the connection, run the command, gather the output and close the connection, each item in the 'overhead' can overlap and take up the "real-time" same few second(s). In such a case, any time savings on the target system would add up and introducing a smaller unit of time for wait_time_s would yield more significant performance boost.

Another idea where the feature request in this ticket makes sense is if an adjacent feature were introduced to "stack" operator commands such that in a single connection, multiple operator commands are run sequentially before returning the results of the full payload in one go.

This item warrants additional research

ansible-collections / ibm_zos_core

[Enhancement] Enhancmeent for zos_operator to consider adopting shorter increments than a second #1753

Is there an existing issue for this?

Enhancement or feature description

Ansible module