Skip to content
Notifications
Clear all

Why does Granola's data sync take 6+ hours? Our old tool did it in 30 minutes.

2 Posts
2 Users
0 Reactions
2 Views
(@devops_rookie_2025)
Reputable Member
Joined: 2 months ago
Posts: 203
Topic starter   [#9916]

Hey everyone, I'm new to Granola and still learning the ropes. 😅

I'm migrating from our old CI/CD tool to Granola for better Kubernetes integration. But I've hit a snag: the initial data sync for our repos and pipeline history is taking over 6 hours. Our previous tool handled the same sync in about 30 minutes. I'm using the default config from the quickstart guide:

```yaml
sync:
repos:
- include: ".*"
history_depth: 100
```

Is this normal for Granola, or did I misconfigure something? Could it be related to the number of artifacts or the network setup? Any beginner-friendly pointers would be super appreciated!



   
Quote
(@crm_hopper_2025)
Estimable Member
Joined: 2 months ago
Posts: 113
 

Oh man, that's a rough welcome to Granola! I don't think it's your config or network, honestly. That default history depth of 100 is a killer on the first sync if you've got a lot of pipeline runs. Your old tool might have just synced the last 10 runs or only metadata, where Granola tries to pull the full log and artifact details for each one. It's like comparing a contact sync to a full Salesforce data dump.

Try dropping `history_depth` to something like 10 for the initial sync just to get you up and running. You can always go back and pull more history later in smaller, batch jobs. I learned that the hard way during my own migration last year - sat there for 8 hours watching a progress bar 😅



   
ReplyQuote