Performance - Overall WF System Performance Improvements

[#1]

The biggest request I have is for a focus on general performance improvements across Workfront. This would be to address many of the following concerns and real-life problems users experience in the system - not just the spikes when there's an outage or degradation.

504 errors.

Slow report loading.

Slow loads on the My Work page.

Slow loads when building new tasks into a project plan or drag & drop.

Sporadic crashing when trying to load a page that's going slowly (I think time out is what's happening when you get stuck loading a report)

Beyond this, it would be nice to get more feedback as far as what's happening with these improvements over time.

This is the single biggest concern across my organization. Performance beats out any feature request we could ever make.

There's an article about upcoming performance improvements on the help site (thanks Heather) but unfortunately it doesn't show when it was posted and it doesn't provide any sort of timing (even tentative timing) on when these updates might be made. I llinked to the article on 4/14/17 so at least there's a reference to when I became aware it existed.

There's also a forum post on the community form located here.

[#2]

Absolutely. Features are important but all of the functionality in the application doesn't mean anything when the app is unusable or unreliable because of performance problems and overall slowness.

[#3]

Recently, the Workfront Customer Care team asked that we authorize them to close out our performance related tickets (each of the items highlighted above). As an alternative of tracking and monitoring resolution of the problem rather than through their ticketing tool, they asked us to check the page below for updates. Didn't hear much talked about this topic during LEAP (general sessions or breakout sessions), but I am hopeful that this will get resolved soon.

Upcoming Performance Improvements: https://support.workfront.com/hc/en-us/articles/115003544908-Upcoming-Performance-Improvements

[#4]

Hi Heather, thanks for sharing the link to that article. I had no idea it existed.

It doesn't appear to provide any concrete dates in the article on estimates for including in the roadmap. It's interesting as the language in the article sounds exactly like language I heard at LEAP 2016. I wonder if this went up shortly after or if it's more recent... I wish there were some sort of date associated with the article so you could tell how long it's been there or when the last update to it was.

In case it's helpful, there was another session at LEAP 2017 that was meant to address the plan for performance improvements but again, no estimated timing to go with it. That's why I put this idea in here on the exchange to try and get some more users to up-vote it and show Workfront how important this is. I think that LEAP session was a hidden one for clients that have complained the most or loudest - I didn't see it on the event schedule anywhere.

[#5]

We also have ongoing performance issues, however, our seem to be related to our corporate proxy server. No matter what we do, we can't seem to clear this up. The performance difference is clear when doing a training or other activity via webex that is completely off our network. We would LOVE to hear from other organizations who may have resolved the firewall issues (without whitelisting fully - we are healthcare and cannot do that). Thanks!

[#6]

Thanks for sharing that link!

[#7]

I notice with large projects with over 100 tasks the performance begins to degrage...this is difficult especially when you need to present project timelines to large groups or executives and want to share the collaborative power of the tool but often that if overshadowed by slow performance of the tool moving from task to task, changing status or updating real time.

MS project does not have this issue since it is not hosted and loaded locally on your work station.

I would love a tool in WorkFront to allow us to "image and work locally" temporarily, store all the changes and then reconnect to host and allow all the updating to take place at that time instead of burdening the entire worksession to unknowable bandwidth...