Hermes provides several configuration options that users can tweak to optimize its performance to suit specific requirements. This guide provides an overview of these options, and suggests ways to modify them for different scenarios.
The two per-chain configuration options you can use to tune the performance of Hermes as of version 1.5 are
1. Trusted Node
trusted_node setting is an experimental option that determines whether or not the full node is trusted.
trusted_node = false
When set to
true, Hermes trusts the full node and does not verify headers included in the
ClientUpdate message using the light client.
This could lead to faster processing as it bypasses the verification step.
However, it's important to note that when the full node is configured as trusted, the verification traces will not be provided. This could potentially lead to failure in client updates after a significant change in validator sets.
If you prefer security over speed, or if the validator set changes frequently, consider leaving this setting as
false, which is also the default.
2. Batch Delay
batch_delay setting dictates the delay until an event batch is emitted if no
NewBlock events have been received yet.
batch_delay = '500ms'
batch_delay values will result in faster event processing, improving the latency of Hermes.
However, setting it too low could sometimes cause events to be split across more batches than necessary, which will then cause Hermes to send more client updates than otherwise required.
Conversely, higher values will increase the latency of Hermes, but will minimize the number of client updates.
If you prioritize processing speed and can tolerate the potentially slightly higher costs, consider setting a lower
batch_delay. For backup relayer or settings where latency is not as important, consider a higher
500ms provides a good balance between speed and reliability, while still minimizing the number of client updates to send.
The tuning of Hermes performance relies on the balance between processing speed and reliability. Keep in mind that tuning these configurations according to your needs could significantly improve the performance of your Hermes instance. Please thoroughly test any changes in a controlled environment before implementing them in a production setting.
Remember, every blockchain and network has unique characteristics that can affect the performance of the relayer, so there's no one-size-fits-all configuration. Feel free to experiment and fine-tune these settings to achieve optimal performance for your specific use case.