eth_logs
in the goldsky
schema, with the secret A_MYSQL_SECRET
created above.
sink_buffer_max_rows
setting controls how many rows are batched into a single insert statement. Depending on the size of the events, you can increase this to help with write performance. 1000
is a good number to start with. The pipeline will collect data until the batch is full, or until the sink_buffer_interval
is met.
EBS baseline I/O
performance as burst credits are easily used up in a backfill scenario.
Aurora I/O optimized
, which charges for more storage, but gives you immense savings on I/O credits. If you’re streaming the entire chain into your database, or have a very active subgraph, these savings can be considerable, and the disk performance is significantly more stable and results in more stable CPU usage pattern.