81–90 of 305 posts
Cloudflare has this as well: >you will not and you have no right to: ... (f) perform or publish any benchmark tests or analyses relating to the Cloud Services without Cloudflare’s written consent; https://www.cloudflare.com/terms/#react-modal:~:text=(f)%20p...
Earlier quoted context omitted.
We have certainly heard from some customers that agree that 'everything' is slow, but we've also heard from other customers saying they have no problems. We would love to fix "everything", and we have some longer term projects focused on this -> However, "everything" fixes seem to be a more incremental boost and also take longer time to complete. If you have any feedback about "specific" items that are the most frust…
> but we've also heard from other customers saying they have no problems I am sorry, there are probably customers who are used to the tools. Maybe they don't pass the Mom test. That point comes out as unnecessary defense here.
Earlier quoted context omitted.
These are questions I have as well. That said, creating a throwaway and prefacing a comment with "Not trying to be snarky" shouldn't be an excuse for not taking the time to couch questions in a way you're more confident aren't going to be interpreted in a negative way. This isn't directed just at you: I see this behavior all too often: people using throwaways as an excuse to not take the time to express things in a m…
If you need tips or TRICKS to make a product useable, you have a BAD product.
If you have to use Jira or Confluence at work, you probably want to know how to make that as useful as possible. If you're working at Atlassian, you probably want to make your customer's experience as enjoyable as possible as soon as possible. Ideally you have a great product and great documentation and all happy customers. If that's not the case, you have an opportunity to work on a number of fronts, including improving documentation and the product, and help current customers with the product as it is. You can and should be doing all of these things.
Piling on doesn't help anything.
Earlier quoted context omitted.
> Trying to do A/B/C is annoyingly slow - etc ? [...] We're trying to focus on frustrating pages/experiences rather than number of network calls It's not really a problem with a certain page or a certain action: it's a systemic issue, that can only be solved with a systemic change. This has come up before here in HN [1]. From my point of view, ignoring the issue around number of calls/performance and all feedback reg…
Hi ratww, Thank you for reiterating this point, and I'll try to shed some light on this. We actually are working on systemic changes to try to make this lighter/better but I can't talk about specifics until the feature is available. On the other hand, any level of specificity is great, for example: 1) full page loads are slower and more annoying than Transitions (or, vice versa) 2) loading Home page is slower and mor…
One of the most obvious examples: they have multiple WYSIWYG editor implementations which aren’t compatible. When you format something in Jira it’ll look fine in the preview and then render differently on reload. It’s been like that for years, nobody cares.
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.
1) markdown macro (limits markdown to the body content, and not interacting with other macros or styling)
2) copy/paste markdown -> autoconvert to WYSIWYG (limits markdown to copy/pasting, so no editing Markdown inside)
3) "markdown pages" (something like 'this page is Markdown only, no WYSIWYG)
I make no comments/promises on any of these becoming real but looking for what's most valuable
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)
If you start using Linear you won't need a benchmark to notice the difference. This is what happens when the "clueless" start "innovating". I've had several conversations over the years with members of Atlassian technical teams. They always wanted to work on performance, but never allowed (priorities). They are in "good" company (Oracle, China, etc.). What's preventing anonymous performance benchmarks, though?
what do they work on? how many other features can you bolt onto an already mediocre wiki? or is it just bugfixes, keeping up with browser quirks, and useless UI "redesigns"/reskins?
Earlier quoted context omitted.
Come on, everything is slow and you know it.
We have certainly heard from some customers that agree that 'everything' is slow, but we've also heard from other customers saying they have no problems. We would love to fix "everything", and we have some longer term projects focused on this -> However, "everything" fixes seem to be a more incremental boost and also take longer time to complete. If you have any feedback about "specific" items that are the most frust…
What do your metrics show? I instrument my web sites so I know how long every operation – server responses, front-end JS changes, etc. – takes and can guide my development accordingly. You have a much larger budget and could be answering this question with hard data.
I’ll second the “everything” responses. Request Tracker on 1990s hardware was considerably faster than Jira is today - and better for serious use, too.
Earlier quoted context omitted.
Navigation is sluggish across the board in both Confluence and Jira. Not just the Cloud service, the self-hosted versions are also painfully slow no matter what resources you throw at them. That makes the other UX issues worse because the feedback loop has so much lag.
Good news about the self-hosted version being slow: Pretty soon you won’t be able to run self-hosted Atlassian products.
Data Center includes a few performance-related features like being able to run multiple frontends. I think we're running 4 instances right now. It's still really slow, even when nobody else is using it.
[1]: https://www.atlassian.com/blog/jira-software/server-vs-data-...