News for hackers. Stuff that matters.
Re:Treating performance as a product: The technical story of... by spollo on Tuesday August 29, 2017 @01:32PM (#15126006)
I can't believe they are patting themselves on the back for performance. I'm running a brand new macbook pro, latest chrome, fiber internet AND asana fully cached. It still is a 6 second initial page load and then every single UI interaction is slow, slow, slow. My entire companies biggest pain point with asana is how insanely slow it is for a simple product.
Re:Treating performance as a product: The technical story of... by infecto on Tuesday August 29, 2017 @01:40PM (#15126081)
This was my largest gripe with Asana and why I was so happy when we moved away from it.

The simplicity of Asana is nice BUT the web app is terrible in how bloated it feels.

I hated clicking Asana links to a task because it would have to load the entire app and wasted what felt like so much time.

Re:Treating performance as a product: The technical story of... by kbd on Tuesday August 29, 2017 @01:43PM (#15126112)
I appreciate that you're not trying to advertise for their competitor, so I'll be that guy... What did you switch to?
Re:Treating performance as a product: The technical story of... by pkaeding on Tuesday August 29, 2017 @02:55PM (#15126714)
I'm not the GP, but we went through a similar journey here, and after ditching Asana, we went to Todoist, which is nice in its simplicity (and fast). Sooner or later, the simplicity became too simple, so we switched to Clubhouse, where we are now. It is serving us well.

Presumably, one day, we will outgrow that, and need to go to JIRA (with all of its power and complexity), but it would be nice to delay that inevitable as long as possible.

Re:Treating performance as a product: The technical story of... by ibrahima on Tuesday August 29, 2017 @04:49PM (#15127488)
Clubhouse is pretty sweet, I feel like it's basically Pivotal Tracker done right. Fast enough to not get in the way but flexible enough for most workflows. We're a pretty small company though, I don't know if something like JIRA becomes more necessary as the company scales.
Re:Treating performance as a product: The technical story of... by spraak on Tuesday August 29, 2017 @04:20PM (#15127296)
We never used Asana, but moved from Trello to Clubhouse as well after we outgrew Trello's simplicity. Clubhouse has been awesome so far, and generally loads quickly
Re:Treating performance as a product: The technical story of... by infecto on Tuesday August 29, 2017 @04:19PM (#15127279)
We moved to JIRA. Lost the simplicity but its a lot snappier and I believe there was some organizational benefits as the company grew.

I am happy that I can click a JIRA link and see a page within a second.

Re:Treating performance as a product: The technical story of... by ugh123 on Tuesday August 29, 2017 @04:31PM (#15127373)
Thats probably dependent on the hardware and size and complexity of workflows and DB size. Our JIRA install is one of the slowest webapps i've seen in a while. Can't wait to move on to something else.
Re:Treating performance as a product: The technical story of... by morj239 on Tuesday August 29, 2017 @04:53PM (#15127516)
Would you mind sharing the approximate number of issues and active users in your JIRA install?
Re:Treating performance as a product: The technical story of... by dasil003 on Tuesday August 29, 2017 @10:20PM (#15129268)
It varies widely. We have ~300 users, 30 projects, probably on the order of ~20k tickets. Performance has been up and down, occasionally things slow way down and we have to file a ticket and then they come back with some excuse about re-indexing or relocating the instance. Normally it's pretty acceptable, but it feels like there are a ton of a variables that go into its performance day-to-day and minute-to-minute.
Re:Treating performance as a product: The technical story of... by ugh123 on Tuesday August 29, 2017 @07:59PM (#15128644)
I'm at a medium/large company, but without access to real numbers i'd say off the top of my head its probably >500 users across 100+ projects and 10s of thousands of issues.
Re:Treating performance as a product: The technical story of... by veidr on Wednesday August 30, 2017 @02:37AM (#15130104)
That seems bananas to me, because JIRA is literally the most painfully slow application I've ever used in my entire career. We use their hosted version, though.

Do you host your own JIRA instance and have somebody in charge of running/tweaking it?

Re:Treating performance as a product: The technical story of... by anotherbrownguy on Wednesday August 30, 2017 @11:08AM (#15132735)
I have used JIRA only many years ago so I can't compare performance with current Asana. When you say JIRA is slow, is it in comparison with Asana?
Re:Treating performance as a product: The technical story of... by azinman2 on Tuesday August 29, 2017 @05:37PM (#15127801)
For me the slowness of JIRA means I loathe going into it. It feels soooo clunky, so 90s in performance and UX. I’m moving to JIRA from trello and it’s night and day. Even something as basic as having a notification inbox with read markers is a paid plugin for JIRA, and everything else seems to require many many clicks (each with their own several second load time). It’s horrible.
Re:Treating performance as a product: The technical story of... by Bjartr on Tuesday August 29, 2017 @05:55PM (#15127942)
Is this self hosted or cloud?
Re:Treating performance as a product: The technical story of... by azinman2 on Tuesday August 29, 2017 @05:58PM (#15127969)
Cloud
Re:Treating performance as a product: The technical story of... by arkitaip on Tuesday August 29, 2017 @02:55PM (#15126716)
I keep going back to Trello for my todo/issue needs. With stuff like Zapier it goes from being simple yet powerful to goddamn nuclear. But I have to be honest here and say that I've never experienced Asana as slow (it's underlying model just doesn't work for me).
Re:Treating performance as a product: The technical story of... by mistermann on Tuesday August 29, 2017 @04:15PM (#15127259)
Curious what you do with Trello and Zapier that is so compelling?
Re:Treating performance as a product: The technical story of... by arkitaip on Tuesday August 29, 2017 @09:33PM (#15129061)
For example, create cards based on email sent to gmail or order cards sent to woo commerce. I have barely scratched the surface of what Trello+Zapier can do but I'm pleasantly surprised that there are tons of ready made 'zaps' for all kinds of app combos.
Re:Treating performance as a product: The technical story of... by johnx123-up on Wednesday August 30, 2017 @01:58AM (#15129986)
FWIW, we switched from Trello to Restyaboard and very happy with its features and speed.

Disclosure: I have suggested few features for Restyaboard and its developers implemented them.

Re:Treating performance as a product: The technical story of... by maccard on Tuesday August 29, 2017 @02:52PM (#15126687)
No affiliation, but even jira is snappier than asana for me.
Re:Treating performance as a product: The technical story of... by aantix on Tuesday August 29, 2017 @04:19PM (#15127291)
Burn!
Re:Treating performance as a product: The technical story of... by nickstefan12 on Tuesday August 29, 2017 @03:33PM (#15126969)
Also not OP, but we've been using dapulse. Terrible name, but it's been working great. It has similar concepts to asana and trello. It loads fast and easy to use.
Re:Treating performance as a product: The technical story of... by landmark3 on Wednesday August 30, 2017 @03:15AM (#15130239)
trello < pivotal tracker (what we use) < jira
Re:Treating performance as a product: The technical story of... by Aeolun on Tuesday August 29, 2017 @11:35PM (#15129544)
Asana was ridiculously simple when we started using it, and I was incredibly happy with it. Then they kept adding, adding and adding irrelevant things, and now I'm pretty put off by it. I wonder if this is a cycle, and a new 'brand-new asana' alternative will spring up soon.
Re:Treating performance as a product: The technical story of... by pspeter3 on Tuesday August 29, 2017 @01:43PM (#15126101)
Page load performance is still a top focus of the company. While page load has improved significantly over the last six months, we know it has a long way to go. Our two largest performance issues are initial HTML time and bundle evaluation time. We're actively working on a solution to both of them.
Re:Treating performance as a product: The technical story of... by spullara on Tuesday August 29, 2017 @01:44PM (#15126124)
Those may be your biggest challenges but he is suggesting that even once it is all loaded it is slow. That should probably take priority over initial load time for an application people are likely to keep open all day. Just look at how long gmail takes to load, it is like forever but doesn't matter nearly as much as how quick it is once loaded.
Re:Treating performance as a product: The technical story of... by pspeter3 on Tuesday August 29, 2017 @01:48PM (#15126156)
Thanks for pointing that out. Our belief is that the majority of in app actions are now fast but that there are still exceptions. We're constantly trying to find new exceptions and remove them. Hopefully this thread alerts us of new ones.
Re:Treating performance as a product: The technical story of... by emfree on Tuesday August 29, 2017 @03:24PM (#15126896)
Curious: What's your strategy for measuring application performance? Would love to hear more details on how you're tracking the effect of your efforts.
Re:Treating performance as a product: The technical story of... by pspeter3 on Tuesday August 29, 2017 @04:55PM (#15127534)
At a high level, we try to collect real user metrics for everything we can. Interana helps us analyze that data in near real time. For more detail, I hope we can write a blog post soon to answer your question.
Re:Treating performance as a product: The technical story of... by pcx on Tuesday August 29, 2017 @01:44PM (#15126116)
In my personal experience Asana is still the snappiest. I've tried Trello, Basecamp and daily use the monstrosity called JIRA. Asana initial load takes a little while, but it hasn't created any problems for me. I always have Asana pinned in my Firefox.
Re:Treating performance as a product: The technical story of... by TremendousJudge on Tuesday August 29, 2017 @01:56PM (#15126210)
is it just me or now it runs faster in Firefox than in Chrome?
Re:Treating performance as a product: The technical story of... by kody on Tuesday August 29, 2017 @02:24PM (#15126467)
I also find that it's much faster in Firefox.
Re:Treating performance as a product: The technical story of... by azinman2 on Tuesday August 29, 2017 @05:42PM (#15127846)
There’s now this dev myth that everything is faster in chrome. Not so anymore. I wish more people would take other browsers more seriously. Personally I find safari the fastest on my Mac, and prefer its font rendering as well.
Re:Treating performance as a product: The technical story of... by efriese on Tuesday August 29, 2017 @10:33PM (#15129316)
We just started using Asana a couple of months ago, but we're not seeing the performance issues some other folks are mentioning. I just hit Asana full refresh and it took 2-3 seconds to render all of the components in My Tasks. It seems pretty snappy in my opinion. Asana with a few Zaps has been great. Because I know they're watching...could you guys add a calendar view to the iOS app? =)
Re:Treating performance as a product: The technical story of... by aantix on Tuesday August 29, 2017 @04:21PM (#15127305)
They should just put a big spinner on the front of the page and asynchronously load everything. Then it'll feel snappy. :rolleyes:
Re:Treating performance as a product: The technical story of... by nwienert on Wednesday August 30, 2017 @08:46PM (#15137300)
Not asana related (or even working in this area) but this piqued my curiosity, would you be able to answer a couple questions? My contact info is in my profile.
Re:Treating performance as a product: The technical story of... by puranjay on Wednesday August 30, 2017 @04:17AM (#15130525)
Agreed. We used Asana but I didn't see the point in paying for a slow product.

Switched the Trello. Never been happier.