Can someone explain how this works?
In a nutshell (eli5) swap is sorta "very slow ram" which is actually just a section of your hard drive /SSD/some other bizarre medium. It is generally used to temporarily store information that might be needed later but would waste valuable "fast ram" which is your actual ram sticks.
What's going on here is this user mounted Google drive in a way that the operating system can interact more directly with it, and it appears to have a set amount of space. Because we've mounted Google Drive we can tell our operating system to use it as swap....very very slow silly swap, but swap nonetheless.
So that's exactly what they did, they told the operating system to set aside X amount of Google Drive for swap, and when looking at the resource monitor we can see the "swap" appears as "more ram".
Hope that helps, please ask if I confused you :)
I'm pretty sure google drive just acts like a syncing tool in the same way as dropbox, so this would still act like a normal swap drive, presumably.
That said, I've only used swap partitions so I'm not sure how it works when you point it at a directory, but I guess it depends how this person set it up.
Thanks <3
So RAM is just memory space that is accessible very quickly by applications that need it. Many applications use it to just temporarily keep information while you have it open. If you have a lot of applications open or you have an application that stores a lot of things even if it doesn't immediately need it all, you can run out of it quickly.
A swap space is a Linux tool (though there are similar things in Windows) that reserves a spot on your hard disk to move data to and from RAM, to keep data that isn't actively being used off the RAM and data that is being used on it. That way you're not as likely to run out of memory from memory-hogging applications.
There's a separate tool to use Google drive space as a disk in Linux. Then, once it's configured as a disk, you can make it act as a swap space. Of course, this is very slow even compared to normal hard disks, but the point is it is possible to do it.
All you need to know is that RAM is all about being extremely fast.
Swap is disk space set aside to be used as virtual Ram (part of your disk become RAM ) for when you have no more real ram. It's useless on modern computers because RAMs are at worst of worst 100 times faster than the fastest SSD. If you have no ram it's just best to crash the OS than making it slow down to a crawl or freeze.
This person use their Google drive as swap which make it even far more useless because even the slowest ssd is probably faster than the best commercial internet connection even with a perfect latency.
In short, it's extremely cursed.
I don't know about useless.
I'm much happier now that my work laptop slows down when I compile something during a zoom meeting, vs when it used to run out of memory and crash.
If you have no ram it’s just best to crash the OS than making it slow down to a crawl or freeze.
That very much depends on what you're doing. Even with rather random access patterns (e.g. compiling) swapping out doesn't crash performance terribly, mostly because my RAM isn't exactly under-dimensioned (I used the rule of thumb "one gig per hardware thread, round up"). For more regular access patterns such as merging SDXL models (which definitely eats all my 16G) the impact is even less. For, dunno, highly complex and irregular datalog queries over a database four times as large as your RAM -- yeah that won't be nearly as fast.
What you also want to do (under linux) is enable the earlyoom daemon. Those freezes are Linux being way too nice and not killing processes until literally every cached and buffered thing has been purged, also heavily-used ones.
Then you'll see behaviour such as switching tabs in the browser, or bringing up a minimised terminal or something actually taking a second or two because they got swapped out. But it's nowhere close to unusable and, due to a 3G/s SSD, a way better experience than in the 90s with a couple megabytes of RAM and swapping to a glorified flywheel.
I could by more RAM, DDR4 prices have pretty much tanked after all, OTOH I swap out like fifteen minutes every other month. Not worth it, I have coffee to make.
A normal swap space is a partition on a hard drive that is used as overflow for ram. It allows the computer to continue working if all the ram is being used.
As far as using google drive as a swap, i have no idea how that would be implemented, but if it's real, the computer would just upload overflow memory to g drive.
It's real, I've seen the blog post from them
Thanks :)
Modern computers are set up so that they can use the SSD/hard drive as extra, much slower RAM. Typically, when normal RAM is full, and you need more, a page of data in RAM will be swapped for a page of data on disk. On Unix, they end up in something called the swap file or swap partition, and on Windows, the equivalent is called the page file. In the screenshot, someone's mounted their Google Drive as a filesystem, and told their computer to use it as the swap partition, so instead of swapping to disk, it swaps to the cloud. This is obviously way slower, but they're effectively now using the cloud as RAM.
it doesn't. LTT tried it and explains why
Here is an alternative Piped link(s):
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
cursed
This brings back memories.
When I was in university, I worked in the computer services department (IT services for the campus). A social science prof down the hall would use a program called SPSS (Statistics Package for Social Sciences) to do various statistics on data sets.
It was available on two platforms: PC & VAX
The PC had about 4 MB of RAM. The VAX (a large centralized computer) had much more (not sure the amount, but I'm guessing around 256 MB at least). The data sets they were using would sometimes require more RAM to process than the PC had (even with swap space), and would give an "out of memory" error.
They always came down the hall and would ask us what to do. The answer was always the same, "Some combination of: get more RAM/swap space for the PC, shrink the data set, simplify the complexity of the query or run it on the VAX server."
They finally started saying, "We connect to VAX, get more memory?"
I don't know if they thought using telnet to connect to the VAX actually caused the local PC to gain RAM or not but it was an inside pun for the department for a couple of years ( ͡° ͜ʖ ͡°) .
Ahh yes.
rclone
