You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting a full history data server is currently a challenging and time-consuming process, as it requires connecting to a P2P node to sync all the historical data. This can take significant time and resources, particularly when the data volume is large.
Solution
Implement a snapshot solution that allows the data server to launch directly against a pre-generated snapshot. Instead of relying on P2P synchronization, the server can load the snapshot to bootstrap its state quickly and efficiently.
Create a snapshot generation process that periodically takes a snapshot of the server's current state.
Provide tooling or documentation to download and validate snapshots.
Allow the server to recognize and load a snapshot at launch
Paths Not Taken
Export data from database
The text was updated successfully, but these errors were encountered:
Summary
Starting a full history data server is currently a challenging and time-consuming process, as it requires connecting to a P2P node to sync all the historical data. This can take significant time and resources, particularly when the data volume is large.
Solution
Implement a snapshot solution that allows the data server to launch directly against a pre-generated snapshot. Instead of relying on P2P synchronization, the server can load the snapshot to bootstrap its state quickly and efficiently.
Create a snapshot generation process that periodically takes a snapshot of the server's current state.
Provide tooling or documentation to download and validate snapshots.
Allow the server to recognize and load a snapshot at launch
Paths Not Taken
Export data from database
The text was updated successfully, but these errors were encountered: