Launchbox High Ram Percentage

[Sbaby]

is it normal that launchbox takes up so much ram? in this last period i have performance problems with my pc's 16gb

 

 

[C-Beats]

To be blunt, it's 2024. 1GB is no longer "a lot", especially for a media intensive application like LaunchBox. You're actively showing another app using almost 6GB ;D. Secondly just because a task shows memory in use in task manager doesn't mean its actually using that full amount on actual RAM. The operating system will push some of the more stagnant bits of data to your page file automatically when the app is in the background and the memory in use is needed.

That being said if you really want to try and reduce the memory footprint you can switch to list view, which should save memory since we aren't loading images. Can also try different themes, as they can display things in a way that takes even more RAM or just has more stuff displayed. You can also hide the game details. Also if trying to pinch RAM Big Box operates far more lean since it doesn't have to load DB definition files that LaunchBox uses and so tends to operate at quite a bit lower usage.

[Sbaby]

I am aware of the game taking up 6gb of ram and on the other monitors I want to keep chrome open with a live tv and do other things on an additional monitor. I've been doing this for many years without any problems, I'll probably now have to increase the ram to 32gb but I also expect a launcher to take up resources like other launchers, not twice as much. 

Anyway thanks for the information ☺️👍 I will try lean modes 

[Sbaby]

13 hours ago, C-Beats said:

To be blunt, it's 2024. 1GB is no longer "a lot", especially for a media intensive application like LaunchBox. You're actively showing another app using almost 6GB ;D. Secondly just because a task shows memory in use in task manager doesn't mean its actually using that full amount on actual RAM. The operating system will push some of the more stagnant bits of data to your page file automatically when the app is in the background and the memory in use is needed.

That being said if you really want to try and reduce the memory footprint you can switch to list view, which should save memory since we aren't loading images. Can also try different themes, as they can display things in a way that takes even more RAM or just has more stuff displayed. You can also hide the game details. Also if trying to pinch RAM Big Box operates far more lean since it doesn't have to load DB definition files that LaunchBox uses and so tends to operate at quite a bit lower usage.

Sorry though, I did some testing and starting for example a tool that improves memory such as Wise Memory Optimizer , launchbox from minimized reduces the percentage of usage to 100mb instead of 1500mb . This could be implemented in the program each time a game is started. I don't see the point of taking up 1.5 gb of memory while playing and launchbox remains minimized. 

[C-Beats]

53 minutes ago, Sbaby said:

Sorry though, I did some testing and starting for example a tool that improves memory such as Wise Memory Optimizer , launchbox from minimized reduces the percentage of usage to 100mb instead of 1500mb . This could be implemented in the program each time a game is started. I don't see the point of taking up 1.5 gb of memory while playing and launchbox remains minimized. 

Again, this could already be happening by the OS. That "optimization" is just shunting the memory of the app into the page file so the OS doesn't have to later, or forcing an OS level garbage collection that wasn't really required yet by the OS (or a combination of the two). Only way to drop the actual memory footprint like that when playing a game would be to dispose all media and dump all cached data from memory. To do so would mean that once you got BACK to LaunchBox or Big Box we'd have to then load it all back up before you could use the interface again which would take several seconds or more. This is also assuming you aren't running any background tasks at the time that requires that information. Then we'd have to pause those processes as well. Most of this would require us to write temp data to a drive that is also now being read from by what ever application you just started which could bottleneck both applications.

[Sbaby]

3 hours ago, C-Beats said:

Again, this could already be happening by the OS. That "optimization" is just shunting the memory of the app into the page file so the OS doesn't have to later, or forcing an OS level garbage collection that wasn't really required yet by the OS (or a combination of the two). Only way to drop the actual memory footprint like that when playing a game would be to dispose all media and dump all cached data from memory. To do so would mean that once you got BACK to LaunchBox or Big Box we'd have to then load it all back up before you could use the interface again which would take several seconds or more. This is also assuming you aren't running any background tasks at the time that requires that information. Then we'd have to pause those processes as well. Most of this would require us to write temp data to a drive that is also now being read from by what ever application you just started which could bottleneck both applications.

With this tool I can play games without any problems, it keeps launchbox memory at bay while it is in the background, upon closing the game the return to launchbox is nice, and I must also tell you that it works better without slowdowns... after closing the game I can navigate inside launchbox between my games very well and of course slowly the memory fills up again but it is correct like that. The only problem is that there is no command line to start this system every time the game is launched, that's why I was asking if it was implemented, it doesn't seem so hard to implement.