The cat is the Rimworld mod with a hefty memory leak yesterday. 32 GB was full in seconds. But it gave me enough time to find the culprit and kill Rimworld without trashing my session every time.
That that to the 3000 browser tabs I have open, two instances of VS code, the multithreaded python app I’m running and developing, the several-gigabytes large dataset that’s active in memory.
For me it's a pattern of "Ctrl+t" to open a new tab and then I search "my interesting query". After that, I use "shift+tab" or "Ctrl+shift+tab" to navigate between tabs. Rinse and repeat until I get tired.
I don't like searching in my current tab because I don't want to lose the info I have.
Oh, here's the 4 pages of documentation of items and crafting recipes of this nodded game I'm playing that are open at all times.
Then there's the tsb with the video series I'm watching, the tab with the dropout home, other two tabs for two series I'd like to watch, about 3 different tabs that I just closed down that were opened yesterday to search some ffxiv market item prices for a friend, WhatsApp web, some Path of exile trade live tabs in case an item I've been searching for a month shows up on trade in a reasonable price to pick up the game again, the medianxl ladder to check for gear on too players, 2-3 tabs for players on the ladder to check their gears as a rough template,...
I'd say at any given time it's a minimum of 10, and I'm not being held responsible of my work browser tabs. That's more like, 4 github repos because they ask me about stuff and I forget to close them, hue, the spark docs on like 5 tabs, 3 google searches, several excels with project tracking stuff, and maybe an extra 10 to 20 tabs open depending of what I'm searching or have been asked about in the last 2 days.
"Simple Tab Groups" extension for Firefox desktop allowed me to evolve from constantly rearranging/bookmarking ~20 shrinking tabs in a window and dropping projects; to hoarding 30-40 tabs worth of research material and unfinished project ideas in rotating groups
Yeah, I'm with you there, but I'm also a believer in having a little more ram than you need. After a couple of decades of feeling that occasional bottleneck it seems like a relatively cheap prevention measure.
When in doubt, blame zoom. The sheer amount of completely different outlandish weird bugs and glitches as well as the fact that they were told what the correct API for screen sharing on Linux is just for them to completely ignore that and do something weird, specific, niche and bad instead … I've never seen something like that since like Windows xp.
I'm completely convinced they have absolutely no idea what they're doing on the frontend (app and web) and just have the latest newbie hire hack things together until it kinda works on their machine.
Just like the human eye can only register 60fps and no more, your computer can only register 4gb of RAM and no more. Anything more than that is just marketing.
This is only true if you’re still using a 32 bit cpu
Bank switching to "fake" the ability to access more address space was a big thing in the 80s...so it's technically possible to access addresses that are wider than the address bus by dividing it up into portions that it can see.
Jokes on you, because i looked into this once. I don't know the exact ms the light-sensitive rods in human eyes need to refresh the chemical anymore but it resulted in about 70 fps, so about 13 ms i guess (the color-sensitive cones are far slower). But psycho-optical effects can drive that number up to 100 fps in LCD displays. Though it looks like you can train yourself with certain computer tasks to follow movements with your eye, being far more sensible to flickering.
It's not about training, eye tracking is just that much more sensitive to pixels jumping
You can immediately see choppy movement when you look around in a 1st person view game. Or if it's an RTS you can see the trail behind your mouse anyway
I can see this choppiness at 280 FPS. The only way to get rid of it is to turn on strobing, but that comes with double images at certain parts of the screen
Just give me a 480 FPS OLED with black frame insertion already, FFS
Well, i do not follow movements (jump to the target) with my eyes and see no difference between 30 and 60 FPS, run comfortably Ark Survival on my iGPU at 20 FPS. And i'm still pretty good in shooters.
Yeah, it's bad that our current tech stack doesn't allow to just change image where change happens.
According to this study, the eye can see a difference as high as 500 fps. While this is a specific scenario, it’s a scenario that could possibly happen in a video game, so I guess it means we can go to around 500 hz monitors before it becomes too much or unnessessary.
The other day I got a Mini PC to use as a home server (including as media server with Kodi).
It has 8GB of RAM, came with some Windows (10 or 11), didn't even try it and wiped it out, put Lubunto on it and a bunch of services along with Kodi.
Even though it's running X in order to have Kodi there and Firefox is open and everything, it's using slightly over 2GB of RAM.
I keep wanting to upgrade it to 16 GB, because, you know, I just like mucking about with hardware and there's the whole new toy feeling, but I look at the memory usage and just can't bring myself around to do it just for fun, as it would be a completelly useless upgrade and not even bright eyed uuh, shinny me can convince adult me to waste 60 bucks on something so utterly completelly useless.
I wish. I use vscode which sucks up most of my resources (basically a terribly inefficient IDE running on elotron...). 32gb and it still not enough to run my dev environment decently.
The reason vscode is so popular is because it is far more efficient than the electron app it's based on. Atom was slow and the worst resource hog I've ever seen.
The plugin ecosystem and great built-in support for the most popular languages keep it popular.
VS Code wasn't based on Atom. It was written from scratch. The system architecture is very different.
VS Code uses Electron, but all the heavy stuff is running in separate threads or processes, which is why it feels faster than some other Electron apps.
Unfortunately, many Electron apps break the #1 rule of desktop app development: Never do any heavy processing on the UI thread. Any Electron app that does heavy-ish processing really needs to use node:worker_threads or something similar, plus a UI library like React that can prioritise handling of user actions over rendering other parts of the UI.
Hate to type this but mate, skill issue. If its taking that much memory check your addons because you fucked up somewhere. I use it with several debugging and linting addons and it runs on a virtual remote desktop where I'm lucky if I have 4GB to share between vscode and the browser with 20 tabs open.
Maybe your issue is thst you ran heavy programs through the vscode console and those registered in the task manager as vscode? Idk, but either way, skill issue :P
Do not underestimate the ram needed just by the lsp. I switch from vscode to nvim, and for some project 8gb is not enough due to that : that part of the memory consumption is sadly not editor-dependant :/
I use neovim (btw) and have it kitted out like a full IDE and it uses about 1gb of RAM at most to run a project. Crazy how much RAM static analysis takes.
I actually do this with NixOS impermanence lol. The things I need are symlinked from a different partition and the stuff I don't need automatically gets wiped clean.
