RPC Edge nodes configuration & priorities
A few more updates on how the team makes our RPC Edge solution more resilient and flexible!
Initial Node Prioritisation with Default Scoring
While dynamic routing and scoring optimise node selection over time, it's crucial that the system starts off in a reasonable state when the server spins up. To address this, we've now implemented a robust approach for default node prioritisation. The priorities are now designed to be easily adjustable, enabling the team to efficiently re-order or disable certain nodes in case of emergencies or other ad-hoc situations. This step ensures more flexibility and efficiency in managing the initial order of nodes, creating a smoother path for ongoing improvements.
Changes made recently in this regard:
- Node Default Prioritisation: we are now configuring RPC Edge to utilise explicitly set default priorities, supporting granular configurations options (e.g. methods and regions) to ensure that specific node preferences can be applied where needed for the enhanced performance.
- Configuration Schema and Structure: the new schema accommodates the team in efficient management of relevant configuration options, ensuring a clean and scalable system.
- Prioritisation Logic Improvements: sorting and filtering algorithms have been improved and generalised to handle various configurations
- Caching for Performance: in-memory caching for configurations is in place, reducing the load & latency on the system when serving requests for high-load chains.
These changes are being released incrementally as we continue to prioritise the stability and quality of our RPC Edge solution.