Sluggish screens on FR970 during running

looks slow to me; and apparently you agree in the comments of your reddit post

"The maps are laggy as others said, however when you run/walk/hike you are only concerned only with a particular sq mt area to see around your surrounding so you can navigate,, you are not gonna see what are things 10mi away from you. So technically the maps are slow i agree, but having a fast loading maps wouldnt have created any difference imo.

garmin is a multibillions company, their experts know more than what people usually argue online. So garmin has to maintain the balance of performance and battery."

I understand that the functionality is not important to some users, but with my 955 solar I actually did use maps to look at trails that required me to pan around. it doesn't have to be 10mi away it can literally be a few hundred meters away and you'd need to pan, at which point lagginess is painful.

I took a look at some other watch (coros/suunto) map speeds and they are wayyyy better. Garmin is falling behind here; if they need a more minimal version of maps to improve performance they should have that as an option.

100%

So i am the one that posted on a separate thread about maps specifically but let me also be as clear on it again (if not more here). 

The "Navigate" function on the 970 is UNUSABLE in PRACTICE!!  If you are reading this and plan to use maps, do not buy this watch. 

Let me be clear as day here:  Not just slow, not just frustrating, but in practice on a run, in a new area, ABSOLUTELY GARBAGE.  SO lets use actual experience here as this has happened to me already 3-4x and i learned i just can not use it. 

I like to run new areas all the time.  SO lets say I want to run a new area. This is supposed to be FUN.  I go to garmin connect and use the "plan a course" feature, which is not w/o some issues, but overall AWESOME.  Send to phone.  Ready to rock.  This is such a cool feature. 

Now, once out there precisely because i am running in a new area, i want a fast responsive map so i do not get lost or take the wrong trail.  But once out there it is so slow to zoom or even to give directions I am going to go as far as to state the current feature is downright dangerous. And this is standing in one place.  Forget about checking directions while on a run.  Multiple time i have been left standing there for a few minutes to verify and double check where i was.  But worse, the attaced "voice directions" are just as bad.  I have had it tell me to go sharp right when there was no trail to the right anywhere, and in fact had to make a sharp left. 

Garmin, clearly this is a huge issue.  The sad part is i have plenty of space on my watch and could easily cache the whole area into memory, so something is not playing nice.  If it is the CPU dictating this, it is sadly under-powered. 

Anyway this topic has been beat to death. If garmin wants to reach out to me and make it right, please do. (I can easily show the routes where i got "lost" with it but lets be honest that is not really the issue. 

I paid full price on it, and would love to have gotten it for 20% off but i didnt.  That's on me. I certainly do not want to return it and plus that is not at all fair to REI where i bought it. But man, a feature i though i was going to love not being usable is just a huuuge bummer. 

On the bright side, the flashlight is awesome, (pun intended). 

Going through the answers and where i see @garmin-hanah menion that

It sounds like the CPU is being overloaded during a very long run when using a lot more features. 

This outright doesnt sound right to me. 
garmin has not upgraded any hardware within 970 it looks like.

they just brought over 965 internals as is into 970 with newer garmin OS skin. They definitely control the features via software. Now it feels like what 970 can do can be easily be done by Vivoactive 5 its just software lock preventing it.

all garmin watches share same processor? Low ram. Are we in 1990?

​I can absolutely confirm that this map rotation slowness is dramatic!

​It's completely unacceptable for an expensive watch to exhibit this kind of performance when the predecessor, the 965, functioned perfectly fine. This map lag, especially with "track up" orientation, fundamentally breaks the navigation experience.
​
​To compound the issue, I've noticed that the Spotify functionality becomes incredibly sluggish when navigation is active. This points to broader performance and resource allocation problems within the watch's software.
​
​I've opened a ticket with Garmin support, but the initial response suggesting that this "is how it should be" is deeply disappointing. Garmin's customer service has certainly been better in the past. I sincerely hope that a proper resolution to these serious performance issues is delivered soon.