Live data from Hacker News

Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

atlassian.com

31–40 of 305 posts

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#31

Nothing says “great product” like a ToS that bans you from discussing the problems. I self-host a confluence install, and it’s performance is poor even with a good sized VM and absolutely zero other traffic to it.

"I won't comment on the performance, but let's just say there's a reason their TOS forbids talking about it."

If you ban objective criticism, I guess all you're left with is FUD.

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#32

Nothing says “great product” like a ToS that bans you from discussing the problems. I self-host a confluence install, and it’s performance is poor even with a good sized VM and absolutely zero other traffic to it.

Yep Confluence is an amazingly overly complicated thing! I had it on modern windows server that boots up in 60 seconds. From that time, confluence starting up take no less than 10 minutes before it responds to web requests. Fortunately we switched to Teams this year, no more exorbitant confluence renewal fees and clueless support.

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#33
Both cloud and on prem user here. Both systems are slow, hardware doesnt scale. Simply browsing issues easily takes 2 to 5 seconds per click. Confluences is okay i guess, just the slowness is annoying. That, and trying to to format text properly.

When youve worked with azure devops or github before, atlassian tooling is really a blast from the past.

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#34

I'm curious, I'm a Cloud customer and I can tell you that the service is incredibly slow even for a small scale setup (2 Jira Projects and 3 Confluence Workspaces). There's an insane amount of network requests seemingly for mouse tracking. By telling everyone here, that Atlassian Cloud products are insufferably slow, am I violating the ToS? I was actually thinking about doing a write up on the issues I've had but thi…

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 ? (edit: looks like HN is severely limiting my reply rate so apologies for delays) We're trying to focus on frustrating pages/experiences rather than number…

Know what would be great? Markdown support. The WYSIYG is full of bad assumptions and has been forever. In the beginning, we could at least opt out but that's long gone. I actively encourage companies I consult for to use anything but confluence because it seems to be designed specifically for the lowest common denominator with no allowance for people who work faster with a keyboard.

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#35

Atlassian Cloud customer here. Large enterprise. The Jira and Confluence cloud products are slow as fuuuuuck.

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 ? (edit: looks like HN is severely limiting my reply rate so apologies for delays)

Come on, everything is slow and you know it.

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#36
post #29

Earlier quoted context omitted.

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 ? (edit: looks like HN is severely limiting my reply rate so apologies for delays)

Not GP but I also have the same feeling across Atlassian products: it is more like a general feeling all the time for many of us. I'm using the latest Firefox on Windows, a developer laptop with 32GB memory that was brand new this spring as well as 500/500 fiber.

Is this also on Cloud products?

Right now on holiday (through Tuesday), but would like learn more. I see your contact info in your profile, if you give consent I'd like send you an email on Wednesday with some followup questions (the first question is "what is the URL for your cloud instance" so I don't want to be asking for it on a public forum)

(edit: typo)

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#37

Nothing says “great product” like a ToS that bans you from discussing the problems. I self-host a confluence install, and it’s performance is poor even with a good sized VM and absolutely zero other traffic to it.

Yep Confluence is an amazingly overly complicated thing! I had it on modern windows server that boots up in 60 seconds. From that time, confluence starting up take no less than 10 minutes before it responds to web requests. Fortunately we switched to Teams this year, no more exorbitant confluence renewal fees and clueless support.

"Yep Confluence is an amazingly overly complicated thing" - yeah,with an incredibly slow editor that screws up even simple page edits constantly. It's a complete shit show. There's a reason we call it "cuntfluence" at my workplace.

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#38

Earlier quoted context omitted.

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 ? (edit: looks like HN is severely limiting my reply rate so apologies for delays) We're trying to focus on frustrating pages/experiences rather than number…

Know what would be great? Markdown support. The WYSIYG is full of bad assumptions and has been forever. In the beginning, we could at least opt out but that's long gone. I actively encourage companies I consult for to use anything but confluence because it seems to be designed specifically for the lowest common denominator with no allowance for people who work faster with a keyboard.

How does this relate to the performance issues being discussed?

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#39

Earlier quoted context omitted.

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 ? (edit: looks like HN is severely limiting my reply rate so apologies for delays) We're trying to focus on frustrating pages/experiences rather than number…

Know what would be great? Markdown support. The WYSIYG is full of bad assumptions and has been forever. In the beginning, we could at least opt out but that's long gone. I actively encourage companies I consult for to use anything but confluence because it seems to be designed specifically for the lowest common denominator with no allowance for people who work faster with a keyboard.

Yes, agreed. I get that confluence is supposed to be for everybody, not just programmers, but there are plenty of great WYSIWYG implementations that use markdown under the hood (and make that accessible). If I could clone the underlying git repo (or an abstraction or something) like Gollum allows, I'd advocate for confluence everywhere. As it stands now I advocate for either markdown/asciidoc in the code, or gitlab wiki (which allows doing that).

Re: Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

#40
post #38

Earlier quoted context omitted.

Know what would be great? Markdown support. The WYSIYG is full of bad assumptions and has been forever. In the beginning, we could at least opt out but that's long gone. I actively encourage companies I consult for to use anything but confluence because it seems to be designed specifically for the lowest common denominator with no allowance for people who work faster with a keyboard.

How does this relate to the performance issues being discussed?

Not GP, but I'd say because it's heavy, and if you didn't have to use it (as there are alternative methods) then you don't pay the performance penalty.
Post reply on HN