Based on what others have said, you probably should increase that by anywhere from 10x to 50x. If you have a spare NVMe slot, you might just add a QLC drive with good read performance for it. For a rig so high-end as yours, that shouldn't be unreasonable.
Where a cache flips efficiency vs. size is hard to tell, if you don't know the algorithms behind: eventually it could add latency if it became too big and wasn't properly managed.
I got plenty of PCIe v4 NVMe (dual WD850X 4TB on that machine), so I could add a TB or two if I felt that would do any good. I just went initially with 10x what it had set on its own and I'll freely admit that 32GB seems puny on a system with 96GB of RAM (Zen 4 doesn't like quad RAM modules like Zen 3 did).
But it really doesn't make a difference in terms of quality of the data, especially when you're just staying with a certain area and it would have downloaded it all long ago. I'm not observing significant Internet traffic flow when FS is running, just what it's using for ATC text to speech I guess.
With Microsoft cancelling Mixed Reality, my HP Reverb Pro headset is going into forced retirement next year so I've been testing a Meta Quest 3 to see if it holds up to a similar level of visual quality: the raw data specs seem to imply so, but only with a cabled (USB3) connection the quality of the video stream seems within a similar range... And I think the Reverb still looks better, while it's also lighter without a battery or much (unneeded) intelligence inside the headset for sit-down VR.
I hate having to spend the extra €500 for no real benefit except a new lease of life, but that's just another M$ gripe.
And I've already bought nearly every Oculus since the DK1.
Anyhow, during the last week I've flown around the airport, the big city next, and my house on the other side extensively to test the various render quality settings and it's got all available data in the cache already, which just stays abysmal in quality.
And it's the very same data and false renderings it was since the last time I tried a few months ago, after upgrading from the 5950X to a 7950X3D, which did quite a bit for the outside world rendering speed on the RTX 4090: finally all technical limits were removed, only to show the ugly truth in high-resolution and quality motion detail...
M$ just doesn't have the data and it's clearly visible on Bing vs Google Maps, nothing software or hardware can fix.
And it became truly comical when I tried to fly over my French branch office in Lyon, only to find it being converted into an old factory building when I got close: interesting to see how the city transformed in three or four decades, but not the experience I was looking for! And in the Paris office they got the outline right, but the visual representation had nothing to do with how it actually looks. If it's not an outright hand-crafted landmark, it's a piss poor guestimate.
And for those landmarks, Google street view does a much better job, especially in VR.
No I don't particularly like Google (quite the opposite, really), but in this case they quite simply have the only data set (in select regions) which might be able to deliver what M$ tries to sell.