Página de la tienda
Cities: Skylines
Todo Discusiones Capturas Artwork Retransmisiones Vídeos Workshop Noticias Guías Reseñas

Cities: Skylines

Página de la tienda
Cities: Skylines >  Workshop > Workshop de thale5 > Loading Screen Mod > Discusiones
Loading Screen Mod
Descripción Discusiones93 Comentarios3445 Notas sobre cambios
thunderbros99 6 OCT 2020 a las 18:01
Numbers question
I'm sorry if this has been asked before, but I didn't see it in any of the discussions...

I understand how this mod works, and what it's displaying, but I don't know Unity, and something's not adding up, so I figured this is the best place to ask.

I'm running windows 10 with 64GB of RAM and a 64GB pagefile. My heavily modded game shows 33.7GB / 37.8GB just as it finishes loading, and both numbers are white. With so much RAM available, there shouldn't be any pagefile use, so I was trying to figure out the 4GB difference in the numbers. I exited the game, set my pagefile to 1000MB (the smallest possible), and reloaded the game. I got the same numbers top and bottom. I exited again, and reloaded, but this time in tabbed mode and with task manager open. The numbers again we're the same, and I was using 57% of my total system memory, which would be roughly 37-38GB. I tried one last test, and opened Photoshop before loading CS. The top number stayed the same, and the bottom number went up to 41.2GB.

Based on this, it looks like the bottom number isn't just CS memory, but the total system memory being used?

Is my math off? Am I missing something? It wouldn't be the first time, lol.

*edit*. By the way, I forgot to add that this is an AMAZING mod, and is a definite must have. Thank you for all the hard work that went into this
Última edición por thunderbros99; 6 OCT 2020 a las 18:55
< >
Mostrando 1-1 de 1 comentarios
thale5  [desarrollador] 11 OCT 2020 a las 4:05 
The math is fine but the way virtual memory works is quite sophisticated.

When an application needs memory, that memory is immediately reserved as virtual memory. However, the memory space is *not* allocated as RAM before it is actually needed, i.e. read from or written to. The CPU and operating system take care of all that. Applications just reserve memory and then access the memory sooner or later.

So, that 4 GB consists of reserved memory that has not been actually needed yet.

The 10% difference you noticed is quite constant for CS (for some apps, the difference is much bigger - my Steam client shows right now 97 MB RAM, 215 MB VM).

It is also fine if some of the reserved memory is never actually needed. VM reservations are basically just advance bookings and carry very little cost.

I guess that is why they use the word "commit" rather than "allocate" with VM reservations.
#1
< >
Mostrando 1-1 de 1 comentarios
Por página: 1530 50