In the DA_SDK, Page 248/577 it says re Deduplication:
Use generous values for the deduplication time. It should be large enough such that you can assume the command was permanently lost if the deduplication time has passed and you still don’t observe any effect of the command on the ledger (i.e. you don’t see a transaction with the command ID via the transaction service).
The setting of command IDs deterministically makes sense but after going through the in-document links from Deduplication > Ledger API > Deduplication Time > Google Protobuf I am still none the wiser.
@cocreature asked a question in relation to
I followed through that thread and see the mechanics behind
min_ledger_time_abs etc. From that, it seems that the only way to accurately assess & implement these boundaries is to execute your commands, benchmarking their performance, then editing the time-related settings as required?
Is that a reasonable premise or is there a more acceptable start figure of 15 seconds etc?