Skip to content

Optimize CI index backfilling processes #5568

@elmattic

Description

@elmattic

Summary

This is a follow up issue of #5360.

Current behavior:
Our backfilling process uses an excessively large number of epochs (300) for both Forest and Lotus. This value could be reduced and adjusted to better align with the requirements of our api compare services (10-ish).

Proposed change:
Remove all hardcoded values in the YAML files or Rust code. Consider exposing a flag in forest-tool api serve to specify the number of epochs to backfill, limiting it to the required amount.

Completion Criteria

  • All CI checks are passing

Additional Links & Resources

n/a

Metadata

Metadata

Assignees

Labels

Type: TaskDiscrete task to implement

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions