I don’t share the same experiences with slowness (maybe we do something right on the instances we manage). I do however experience slowness in cloud. I assume they increase cloud resources in some kinds of steps that make them appear extremely sluggish.
Sorry to hear it's been a frustrating experience. I'm a PM for Confluence Cloud and we're always trying to make it better. Would you be willing to share more specifics, such as:
- Pages with content X are the slowest
- Trying to do A/B/C is annoyingly slow
- etc
?
You should be able to experience the slowness for yourself by spending a few minutes using your product. Then try something like notion or pretty much any other web app and notice how your blood pressure drops and your stress levels decrease.
It is not a particular area it is the whole thing. Every interaction makes me want to gouge my own eyes out. It's a glorified text area with a menu, why should every click cause dozens of requests that take more than 10 seconds to complete?
I can only conclude Atlassian engineering is utterly disfunctional for this to have gone on so long unimproved.
We definitely recognize we have a lot of work to do on performance in general, and we're definitely trying. "fixing everything" is definitely part of our plans, but we'd also like to "fix whatever users find the most frustrating".
If any specific items stand out as the most frustrating please do let us know.
Thank you for the insight. We are definitely working on generalized efforts to make 'most/all/everything' faster (including speeding up the app overhead), but those types of projects unsurprisingly take a little longer to finish.
On the other hand, specific user feedback might be 'the most annoying thing to me is that pages with Links load slowly, I need the links to load earlier because of X', or 'I need inline comments to load faster than page comments, because of reason Y'
-> this type of feedback could give us something we can fix quickly and alleviate user frustration sooner. Hopefully the intention makes sense.
Of course, in general, we're also always looking for any feedback that can help us improve Confluence!
Your response seems to show the problem. Trying to add little quick fixes might sound reasonable from a business perspective, but it's not going to help on the tech side. If anything it's going to make matters worse.
Thanks for the consideration - we are working on big fixes as well, but can't share information about those until we are closer to shipping. In the mean time we're open to suggestions and feedback of all types.
Where is the data hosted? Somehow it feels like the devs are located close to the data and don't notice the lag. And for me in central Europe, some requests must travel across the world and back.
My original post did not mean to give the impression we think Confluence is fast - we do recognize that we have a lot of room for improvement.
The reason we're asking for feedback on specific areas that are annoying is that while we can work on making 'everything' faster, knowing which specific items may be of the most concern may allow us to focus fix those items first.
If you do have any feedback around such specific items we would be happy if you're willing to share it.
We have a lot of metrics, and we recognize that Confluence is not as fast or as good an experience as it should be.
However nothing beats user feedback - hearing specific feedback from users may provide us with specific areas that we can focus our work, on top of the work we're already doing.
If you have any feedback like that, we're hopeful you're willing to share it with us.
I agree with you on user feedback being valuable, but not to figure out what's slow. You should be getting that information accurately through metrics and know what to prioritise without having to speak to anyone. Reserve questions you can't get answers for otherwise for user interviews.
