Skip to content
Notifications
Clear all

Why is Fellow so slow with large meeting histories?

5 Posts
5 Users
0 Reactions
76 Views
(@lindseyw)
Active Member
Joined: 4 months ago
Posts: 9
Topic starter   [#8147]

I've been using Fellow for about six months to manage team meetings. We're a sales team, so our meeting notes, agendas, and action items are critical.

Lately, as my meeting history has grown (probably 300+ meetings now), the app feels sluggish. Opening the main dashboard or searching for a past note takes a noticeable few seconds. It's most apparent on the web app. Has anyone else experienced this with a large volume of historical data? I'm wondering if it's a known issue or if there's a setting I'm missing to improve performance. I love the features, but the lag is starting to impact my workflow.



   
Quote
(@clara12)
Estimable Member
Joined: 4 months ago
Posts: 210
 

I've noticed this too as our design review history has grown, though it's not quite as severe on my end. You mentioned it's most apparent on the web app, which makes me wonder if it's a client-side rendering issue. Have you checked whether the performance is consistently slow across different browsers, or if it's tied to a specific one, like Chrome?

It seems like a common scaling challenge for note-taking apps that rely heavily on a single, continuously updating view. I'm curious if anyone has found a practical workaround, like exporting older meeting archives to reduce the active dataset, or if the performance is inherent to how the dashboard queries the entire history every time.



   
ReplyQuote
(@jackm)
Trusted Member
Joined: 4 months ago
Posts: 46
 

I use Chrome and have tried Firefox, but it's slow in both for me. The export idea is interesting. Does Fellow even have a bulk export feature, or would you have to do meetings one by one? That seems like a lot of manual work just to maybe fix the lag.



   
ReplyQuote
(@ci_cd_junkie)
Honorable Member
Joined: 8 months ago
Posts: 476
 

Yeah, the 300+ meeting mark feels like a real tipping point. I suspect it's less about browser choice and more about how they're handling that local dataset on load. There's no client-side pagination or lazy loading happening. It's likely trying to hydrate the entire meeting history into your browser's memory every time you open the dashboard, which for 300 complex objects with notes and action items is... heavy.

Have you tried the desktop app? Sometimes electron apps handle this a bit better because they can use a local database more directly. If the web app is just a React SPA hitting an API, the slowness is probably from fetching and processing that giant JSON payload before anything renders.

No magic setting, unfortunately. You might need to ping their support - this is a classic scaling issue they should be fixing with paginated API calls.


pipeline all the things


   
ReplyQuote
(@cloud_cost_hawk_2)
Honorable Member
Joined: 7 months ago
Posts: 472
 

Good call on the desktop app theory, that's exactly where my mind went too. It's the classic cloud app architectural tax - a heavy SPA frontend trying to swallow the entire data lake in one gulp.

Your point about the 300+ object payload is the real killer, though. I've seen this pattern before in other tools. It's not just the network fetch, it's the client-side processing and the memory overhead for all those rich text objects. Even if they're using something like IndexedDB locally, a poorly optimized query can still feel like mud.

Makes you wonder if they're leaning on something like a GraphQL API without proper cursor-based pagination. You'd think pagination would be a day-one feature for a meeting history view.



   
ReplyQuote