RollingCache.ccc performance debugging … under SU3

2025.08.31 - v1.5.27.0 - Launch times and server availability

During 2024 I … and most likely everybody else … have seen the following FS2024 alert veeeeery often:

“Bandwidth too low, loading times may be extended and world streaming degraded”

This alert “nicely” correlated with:

  • Excessive launch times.
  • Incomplete aircraft and mysterious landscapes.
  • Poor or stuttering FPS … at least as far as I remember.
  • A lot of FS2024 frustration … and some “mea culpa” Dev Stream statements.

Starting in S1 the “Bandwidth” alert has became a lot less frequent and since SU2 I cannot remember having seen that alert anymore.

Server availability

On my end there have not been any changes in hardware or network connection (500 Mbps fiber-optic) since the launch of FS2024. So from that perspective I would conclude that:

  • FS2024 backend API and CDN servers seems to be (a lot) less stressed today
    • … than during the initial first month after the launch.

The reason for this improvement is basically impossible to know from the outside.

  • Either the FS2024 team did simply increase the server capacities
    • … or “tuned” the contract they have with the CDN
    • … or changed the configuration of the CDN caching rules
    • … or … whatever.
  • Maybe … the FS2024 client code did improve (a lot?)
    • … and better local caching of data did reduce the stress on the backend servers enough
    • … or mainly the interaction with the servers has become more robust.
      • (Remember the “client time out of sync with the servers” issue?)
  • … or … everything of the above.

I gave my view on data processing pipelines and especially the role of CDNs like Akamai back in 2025-01.

So far this goose feels like there have not been any fundamental changes to the Rolling Cache subsystem. So I find it most likely that all improvements are related to aspects outside the actual RC code.

Which might be good news … as it could mean that there is still (a lot?) of room for even further improvements.

Sim launch times

Right after the launch of FS2024 I did observe the following launch times of FlightSimulator.exe:

  • below 3 minutes
    • … especially if I had a nicely prefilled Rolling Cache
    • and used the sim while everybody else out there was doing something else (e.g. was sleeping).
  • 3 to 5 minutes
    • was a fairly common launch time
    • … but it also did require a prefilled RC.
  • 5 to 60 minutes
    • was rare … but still happend way too often.
    • It usually correlated with a fresh, empty RC.

So far with SU3 I have observed these launch times:

  • around 3 minutes
    • … is the common duration on my system now.
    • The shortest so far was 2:40 m:s.
  • 4 to 5 minutes
    • … so far only happen when I launched with a fresh, empty RC.
  • 5 to 60 minutes
    • … did not happen once.

Xbox server problems

I have seen the following error when launching the sim for years now …

… and I still see it in 5 to 10% of the FS2024 launches.

However, those errors are coming from the gamelaunchhelper.exe and not the acutal FS2024 code. The problem seems clearly related to Xbox services and servers.

Usually a second launch attempt resolved this error and so this goose kind of got used to it.

To summarize this launch time and server related overview:

  • The “Bandwidth too low” alert is a thing of the past
    • … at least for me with my setup.
    • I guess the main improvements took place on the server (interaction) end
      • … and not the local RC subsystem.
  • SU3 does still need around 3 minutes to launch … on my system
    • … but noticably or excessively longer launch times are a thing of the past.
  • There still seem to be problems with the Xbox “game hub” related services
    • … but IMHO there is nothing that Asobo can do to resolve those issues.