Linux

63443 readers

414 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

What is the proper way, if there is one, to remove files and applications added to ram with preload? (lemmy.ml)

submitted 3 days ago by vortexal@lemmy.ml to c/linux@lemmy.ml

11 comments fedilink hide all child comments

If you're not aware of what preload is, it's a command line application that allows you to add files to ram, so they can be accessed faster by the applications that need them.

It seems to work well for what I'm using it for, which is to run games from slower storage devices, but there doesn't seem to be any documentation for a proper way to remove the files once they've been added to ram. What I've been doing is to just use htop to terminate the preload command, but I feel like this is not intended at all. Is there a better way to remove these files?

I should mention that while trying to search for a solution myself, I did see gopreload mentioned a few times. I would try this out myself, but there's no proper installation instructions, at least not any I could find that work in Linux Mint.

you are viewing a single comment's thread
view the rest of the comments

[–] HelloRoot@lemy.lol 2 points 2 days ago* (last edited 2 days ago) (2 children)

This doesn't really prove it.

Running ths game multiple times will do the same, because the pages will stay cached. Operating systems are smart with RAM. Things that were recently used stay in RAM, even though the OS reports it being "free". Read this for some more info: https://www.linuxatemyram.com/

And preload might swallow the filepath arg without doing anything with it.

Instead you could share the output of

preload --help
preload --version
sudo preload --verbose
# followed by running a game

What you describe can actually be done with another tool https://hoytech.com/vmtouch but not with preload.

[–] vortexal@lemmy.ml 2 points 2 days ago

After trying vmtouch, it only seems to be partially helping. I'm not sure if I'm just using it incorrectly or not but if I remove the files from RAM and then use vmtouch to add them back in, the hitching issues are still partially there.

To fully explain what my issue is, I currently using the Linux version of the Cyber Lancer demo from Itchio as it's small enough to fit onto my 128 MB SD card, which is very slow. I can easily run the game from other storage devices that have much higher read speeds but I want to get the most out of my older and slower storage devices. What's happening is when the game first loads when it's files aren't stored in RAM, is the game essentially freezes for a split second every time it has to load an asset that wasn't previously loaded.

vmtouch isn't making the hitching go away, it just making it load a little faster. This does mean that it'll help but if you're aware of a better solution, I can try that out as well.

[–] vortexal@lemmy.ml 1 points 2 days ago

That wont be necessary, after doing more "extreme" tests with preload, it seems like I was wrong about preload. I used sudo sysctl vm.drop_caches=1 to make sure that none of the game's files were loaded in RAM before using preload like I did yesterday, but the game still has hitching issues. This means that the game's files were probably still loaded in RAM when I was testing it yesterday.

For context, what I'm trying to do is find a way to run smaller games more smoothly from some very old storage devices that are very slow. I thought that preload would be the solution but since it doesn't seem to actually do what I thought it did, I'm going to need a different solution. I will try vmtouch and respond back if it works.