Is this normal?

[mdk5150]

 

I'm downloading some really large mods ATM, but no mods are actually being installed right now. The only one currently downloading is about 2.5GB, but I have some other in the pipe that are even larger.

 

BTW, it's still going up. At the current rate of increase, it should be enough to crash my PC within a couple of hours.

[Guest deleted34304850]

its normal. just leave it.

[rmm200]

You also have the option of downloading your huge mods manually, then dragging them to Vortex.

That way you never see Vortex' memory going up...

 

I can not say one method is really faster than the other. Download through Vortex does tend to pause when you are running a game.

[HadToRegister]

A third option is to manually download your mods to your Vortex Download folder by using the SAVE AS... option in your browser

[mdk5150]

I'm not so much looking for a way to fix it as just wondering why. I went to bed around the time I posted that, and when I came back, it was taking up 30GB in memory, although it did finish downloading my mods without any issues.

 

It seems strange that it would (I'm guessing) allocate space for all downloaded files to RAM even for inactive or queued downloads, and then continue holding all that RAM even after the download has long since been written to HDD. As you guys have said, I can download the same files through my browser, and it'll never come close to taking up 30GB of RAM. Is this some kind of redundancy, or just a glitch in how Vortex uses memory?

[HadToRegister]

I'm not so much looking for a way to fix it as just wondering why. I went to bed around the time I posted that, and when I came back, it was taking up 30GB in memory, although it did finish downloading my mods without any issues.

 

It seems strange that it would (I'm guessing) allocate space for all downloaded files to RAM even for inactive or queued downloads, and then continue holding all that RAM even after the download has long since been written to HDD. As you guys have said, I can download the same files through my browser, and it'll never come close to taking up 30GB of RAM. Is this some kind of redundancy, or just a glitch in how Vortex uses memory?

 

 

Your question was answered, it's normal

There is no Space Allocating going on for downloaded files.

[Guest deleted34304850]

I'm not so much looking for a way to fix it as just wondering why. I went to bed around the time I posted that, and when I came back, it was taking up 30GB in memory, although it did finish downloading my mods without any issues.

 

It seems strange that it would (I'm guessing) allocate space for all downloaded files to RAM even for inactive or queued downloads, and then continue holding all that RAM even after the download has long since been written to HDD. As you guys have said, I can download the same files through my browser, and it'll never come close to taking up 30GB of RAM. Is this some kind of redundancy, or just a glitch in how Vortex uses memory?

that is not even close as to how memory allocation works.

[Tannin42]

RAM is not a fast storage system, that fills up and when it's full you have a problem.

RAM is a slow cache, that will try its best to keep as much information from storage (e.g. disk, internet) accessible quickly. Memory Management keeps track of whether the data is present and up-to-date on storage and when it was last accessed so it can drop low-priority data if necessary.

 

As such, having a lot of memory usage is not a problem per se. In an ideal world your RAM would always be 100% utilized, everything less is a waste of resources you paid for.

The more interesting question of "how much RAM does this application require minimum in a pinch" is not answered by the task manager.

 

Vortex leaves memory management to the backend, we allocate memory that we intend to work with and when we stop working with it, the backend is free to return it at its own discretion. But when that actually is will vary a lot on your system and what other software you run. From experience Vortex (like every chrome-based application btw.) will use more memory on systems that have a lot of memory installed.

That makes it really difficult to see whether Vortex is actually using "too much" memory, it may simply be the backend having no reason to return the memory yet because there is plenty left and freeing memory in large chunks can be better for performance.

 

It should also not affect game performance because if a game actually requires the memory, the OS should be taking anything non-essential back from Vortex.

 

This is not a problem unless we have an actual bug where it looks to the backend like memory is still being used by Vortex even if it's not. If that was the case, it would lead to a Vortex crash after a while.

Again, you can't see this in task manager, you can only see it by Vortex crashing or system performance becoming bad as a result.

[mdk5150]

 

From experience Vortex (like every chrome-based application btw.) will use more memory on systems that have a lot of memory installed. That makes it really difficult to see whether Vortex is actually using "too much" memory, it may simply be the backend having no reason to return the memory yet because there is plenty left and freeing memory in large chunks can be better for performance.

 

Thanks. I had no idea Vortex was Chrome-based, which explains everything.

[Williamzack1]

In simple words its normal :)