Add --duration param to verify-range command

[bartekn]

When testing old ledgers using verify-range (#1848) we should also ensure that speed of ingestion is fast enough. To achieve this we can add --duration param to verify-range that specifies time limit in ms in which ledger should be ingested. If it exceeds the limit, verify-range should print an error and return non-zero exit code.

When it comes to implementation we should probably add timer to pre, post hooks (post hook after commiting to DB).

[bartekn]

Let's skip it for now. I was able to find the slow ledgers using CloudWatch log query. For future reference:

filter @message like /duration=/
| filter @message like /Finished processing ledger/
| parse 'duration=* ledger=* ' as duration, ledger
| filter duration > 5
| sort duration desc

EDIT: query post ingestion refactoring:

filter @message like /duration=/
| filter @message like /Processed ledger/
| parse 'duration=* graph=* ledger=* pid=* sequence=* ' as duration, graph, ledger, pid, sequence
| filter duration > 5
| sort duration desc

[bartekn]

Closing, it's easier to check this by analysing log output.