• Jan Provaznik's avatar
    Load epic issue metadata info in batches · e15a1c73
    Jan Provaznik authored
    If number of epic ids we pass to BulkEpicAggregateLoader reaches a limit
    (~200), then postgres uses a different plan for the query which is much
    slower.
    
    To avoid this situation, we get this metadata in two phases:
    1. get epic ids for epics and its descendants (we use pluck because
    this query is recursive and find_each wouldn't help here)
    2. we iterate in batches and get metadata for each of batch
    e15a1c73
20210219111040_add_epic_issue_composite_index.rb 425 Bytes