We have a problem where one Structure contains a very large amount of data that needs to be displayed to the user all at once when they click on it. My question now is whether we should split all epics into multiple structures, or whether folders and memos could help us here so that not all data is loaded initially, but only the data within a single epic. Our hierarchy is set up so that each department is divided by epic, and everything below a department goes either into a memo or a new structure. We've reached the performance limits in this regard and already feel that 10–15 seconds of loading time for the user is too much. What is the recommended approach here?
Hi @Jurica Petricevic ,
I'd recommend checking the official article on the topic: Performance Considerations
I haven't been working with DC lately, so I can't say much regarding optimizations, but you can also try to reach out to Tempo directly via one of their support channels. From my experience, they could guide you towards some optimal solution that you could use and that would improve general usage optimization when it comes to their products.
Cheers,
Tobi
Hi @Tomislav Tobijas ,
thanks a lot for your quick reply and for pointing me to the official article — I’ll definitely check it out.
Also appreciate the tip about reaching out to Tempo directly. We’ll consider that as the next step if we don’t get further internally. It’s good to know they’ve been helpful in your experience.
Thanks again and best regards,
Jurica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.