Product Discovery - So slow that it has become un-usable
Asked by Chris Carafello:

We started using product discovery for 2024 roadmap planning.

We have roughly \~35 PMs contributing and managing their roadmap deliverable out of PD.

Naturally we have many views of the same data based on filters and what any one audience would want to see. That is one of the main value props of discovery.

We have maybe 3 or 4 calculated columns, vs Coda where we literally had 100s.

We have gotten to the point where every single click takes minutes to refresh, its basically un-usable and need some sort of solution forward. I have been deleting unused views but nothing seems to be helping.

Unsure what number the sequence starts on, but we are approaching ID 17,000

Any ideas?


Answers:
author: Troy Moore
body: Are all being managed in a single PD project? If so, you may want to consider making divisions among PM groups and opening/managing other projects.


author: Tanguy Crusson
body: Hi [@Chris Carafello](/t5/user/viewprofilepage/user-id/5429131) , I've asked the team to investigate.

Am I reading right that you have 17,000 product ideas???

comments: author: Tanguy Crusson
body: Oh, one thing that will help [@Chris Carafello](/t5/user/viewprofilepage/user-id/5429131) would be to give us access to your projects so we can test there directly and offer suggestions. That makes things 10x faster.

To do that you'd need to raise a support ticket.

From Jira Product Discovery:

* Left sidebar: Give feedback
* Choose "Get help from the support team"
* Paste the following message: "Tanguy Crusson from the JPD team asked me to create a support ticket so the JPD team can get access to our JPD project and investigate a performance issue. Can you please help?"
* And submit the feedback

That will create a support ticket and a support person will reply for permission to access your instance.


author: Chris Carafello
body: Our ID is 17,000 but it was artificially increased due to many failed imports that increased the count.


author: Chris Carafello
body: Following the support ticket and access path now.


author: joachim ramberg
body: I had the same problem working on a Thinkpad with i7 (windows/chrome). I switched to Firefox and the performance improved somewhat. I'm now working on a macbook air and it's running very smooth in large JPD projects. My colleagues that are running windows still have some issues tho.

So for me the solution was to switch to apple.


author: Solaiman, Raouf
body: I've noticed the same latency starting to creep in... just added roadmaps for \~35 product teams. Praying scalability isn't an issue as we really like the platform.

comments: author: Chris Carafello
body: I am sure its related to volume, multiple views, and grouping.. however that is literally the use cases for why we are using it.


author: Tanguy Crusson
body: We have a team dedicated to things like this. We've done a lot of improvements over the past months on these topics, I thought the same initially but we found it isn't as simple as what you suggest Chris - usually it's due to a combination of things that are configuration specific (e.g. specific formula calculations) or concurrent usage coupled with real-time updates (which we're revamping). Which is why looking at your instance will help


author: Chris Carafello
body: Tanguy,

I have given you access following the steps you listed. Please let me know next steps, PMs are all reaching out to me about slowness.


author: Tanguy Crusson
body: Thanks! I've asked the support team


Tags: performance