Live data from Hacker News

Transparent memory offloading: more memory at a fraction of the cost and power

engineering.fb.com

11–20 of 62 posts

Re: Transparent memory offloading: more memory at a fraction of the cost and power

#11
post #4

Earlier quoted context omitted.

You should read the whole article, because TMO does differ from traditional swapping. Notably, swapping usually occurs during periods of extreme memory pressure, where as TMO will offload memory much sooner and more intelligently.

So… paging then? Slightly improved paging?

If only there was some way to know! Some kind of... hyperlink, with text, where the answers you seek were available in a language you know, English, perhaps?

Re: Transparent memory offloading: more memory at a fraction of the cost and power

#12
The inevitable, albeit cynic response: Imagine how much DRAM could be saved if Facebook was shut down!

Or put differently: I have only the greatest respect for the Facebook engineers who come up with innovations like this. This one seems to save cost, lowers power use and improves performance all at the same time. If only this engineering talent could be steered to better causes. Facebook is a net negative for society. Here is hoping that emerging “ethical” technology startups eventually have as great of success as surveillance juggernauts Facebook and Google enjoy today.

Re: Transparent memory offloading: more memory at a fraction of the cost and power

#13
post #11

Earlier quoted context omitted.

So… paging then? Slightly improved paging?

If only there was some way to know! Some kind of... hyperlink, with text, where the answers you seek were available in a language you know, English, perhaps?

The linked article practically goes out of its way to obscure how much this work is incrementally building on Linux’s existing paging design versus designing their own solution. Sure there’s a couple places that mention Linux defaults don’t work for them, but it isn’t all that clear how difficult it was to change things

Re: Transparent memory offloading: more memory at a fraction of the cost and power

#15
post #5

>Using a compressed-memory back end, TMO saves 7 percent to12 percent of resident memory across five applications. Multiple applications’ data have poor compressibility, such that offloading to an SSD proves far more effective. that in general sounds strange. My experience across different application types over more than 2 decades has been very different (not about SSD, i mean the compression in memory have been alw…

> …i mean the compression in memory have been always a very efficient approach.

It’s quite possible that a large amount of stuff FB handles is already compressed (e.g. photos, video, and audio) and thus doesn’t offer much opportunity for further compression. Though I wonder how much of that stuff would be memory resident in the back end in the first place.

Re: Transparent memory offloading: more memory at a fraction of the cost and power

#16

Nice, they have reinvented virtual memory and paging to disk.

No this is obviously something supposed to improve on virtual memory and paging to disk. It uses things like that but is supposed to work across a data center with a bunch of different stuff. Improvement for a specific case is not "reinvent".

Re: Transparent memory offloading: more memory at a fraction of the cost and power

#17
post #10

Nice, they have reinvented virtual memory and paging to disk.

did you even read this?

I get that this comment might have struck a nerve with you, but the site guidelines specifically recommend not asking if the commenter read the article.

> Please don't comment on whether someone read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that."

FWIW I don’t think that the parent comment is wrong, but rather over-generalizing. If you’re close to the project, I’d love to hear a proper rebuttal to what seems to be a common question.

Post reply on HN