ZwiftPower Update: Fit File and Metrics Processing Upgraded

ZwiftPower Update: Fit File and Metrics Processing Upgraded

ZwiftPower has been struggling to adequately process rider metrics and fit files for the past few weeks as Zwift usage has soared to unprecedented levels. The backlog had been growing continuously, with the pending metrics exceeding 100k and fit files exceeding 150k as of a few days ago.

This impacted racers in a variety of ways including delaying category upgrades, displaying inaccurate data, and preventing the viewing of specific power numbers for an event.

Inconveniently, the Zwift devs responsible for ZwiftPower were away on holidays when this problem got ugly, which slowed down the implementation of a solution. And concern was growing with Zwift Racing League Season 2 launching on Tuesday, since this will be Zwift’s biggest race series to date!

But here’s some good news for your Friday: I’ve just been informed that today, the problem has been fixed (see the Zwift forum thread.) Where ZwiftPower was previously limited to processing one file at a time, it is now multithreaded and able to process at least 200 per minute according to one source. (It looks to be moving even faster, from what I can see: closer to 300 per minute.)

Will this be enough? It’s certainly an improvement. Time will quickly tell if processing needs to be further boosted.

ZwiftPower’s backlog problem didn’t have a quick fix, from what I’ve heard – it required coding changes on ZwiftPower’s side plus changes to Zwift’s API which is used to grab the files.

Even as I’ve composed this quick post, the backlog of pending metrics and fit files has been shrinking. Here’s where the numbers currently stand:

At 200/minute, those numbers should be at zero by 4:00pm Pacific time. We’ll keep an eye on it and see what happens!

Kudos to Zwift devs for getting the problem resolved. We like to give a little guff to Zwift for moving too slowly or not implementing the features we want, but I think it’s always a good idea to give a thumbs up when it’s due.

About The Author

Eric Schlange

Eric runs Zwift Insider in his spare time when he isn't on the bike or managing various business interests. He lives in Northern California with his beautiful wife, two kids and dog. Follow on Strava

Subscribe
Notify of
guest
20 Comments
oldest
newest most voted
Inline Feedbacks
View all comments
Ryan
Ryan
11 days ago

That current number of fit files in the picture is either very coincidental, or a bug… 65,535 is (2^16 – 1), which is a common value in computer science for overflow or invalid value (it also happens to be “-1” when represented as an unsigned number, but now I’m getting pretty technical).

Chris
Chris
11 days ago

Glad this has been fixed, although the power data that has pulled through has bumped me up to Cat B! 😢🥵

Erik
Erik
11 days ago
Reply to  Chris

Congrats!!

rdcyclist (Mark Crane)
rdcyclist (Mark Crane) (@rdcyclist)
10 days ago
Reply to  Chris

LOL. I feel your pain. I got bumped up last summer and it was less than optimal for me. It’s way more fun to be at the pointy end of the peloton than in the grupetto…

Daniel Pearson
Daniel Pearson (@dpearson)
11 days ago

Kudos to Zwift for taking over Zwift Power over the summer, ruining it, not caring, and finally fixing it! You deserve a lot of credit Zwift! Remember when real peak zwift was hit last year and this didn’t happen lol?

Michael Witzel
Michael Witzel
10 days ago
Reply to  Eric Schlange

200/min? What hardware are they using? C64? At least they heard from multithreading 😉

Allen Day
Allen Day
10 days ago
Reply to  Michael Witzel

“Where ZwiftPower was previously limited to processing one file at a time, it is now multithreaded and able to process at least 200 per minute according to one source.” Exactly what I was thinking. Should we all be happy now that they upgraded to technology used in similar situations 20 years ago? At least Eric was nice enough to give us a little info in this article … It is more than Zwift did.

Kelley Wegeng
Kelley Wegeng (@kwegeng)
11 days ago

It’s definitely shrunk significantly. They’ve already processed the file for ny WTRL TTT last night.

Dennis van Maren
Dennis van Maren
11 days ago
Reply to  Kelley Wegeng

The 3R race from this morning is also already processed! Happy to see this!

Mitchell
Mitchell (@rmpearce1964)
10 days ago

I wasn’t in a hurry to get upgraded anyway…..:)

rdcyclist (Mark Crane)
rdcyclist (Mark Crane) (@rdcyclist)
10 days ago

The number of .fit files to process is at zero currently. Yay.

Sandra Moeller
Sandra Moeller
10 days ago

Cannot be, I am still waiting for Dec. 26th….

naan
naan
10 days ago

That’s how it is displayed, but the actual backlog at the moment is still 3–4 hours worth of race data.

Derek
Derek (@dpr4473)
10 days ago

Zwiftpower was doomed the moment Zwift took control of the site.

rdcyclist (Mark Crane)
rdcyclist (Mark Crane) (@rdcyclist)
8 days ago

As of this morning, Monday, 11Jan, 8am PST it’s completely off the rails. The events aren’t even showing up on users profile page and the event pages only have the start lists of riders that signed up on Zwift at least a day early. SNAFU…

Chip Seabolt
Chip Seabolt
1 day ago

I have 6 races since 10/18/2020 including the start of ZRL season one which are still green (live data) with no race ranking impact. Is there a way to upload my fit file to Zwift or Zwiftpower from each race to replace the live data status and see my race ranking move?

20
0
Would love your thoughts, please comment.x
()
x