Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a269f0a57810ecd4

Jump to content

// Workers AI · dad joke modeWhat did unique set size say? "I'm one of a kind".

From Wikipedia, the free encyclopedia

In computing, unique set size (USS) is the portion of main memory (RAM) occupied by a process which is guaranteed to be private to that process. The unshared memory of a process is reported as USS.[1]

This concept is used for software running under the Linux operating system.[2] It was proposed by Matt Mackall because of the complications that arose when trying to count the "real memory" used by a process.[3] The concepts of resident set size or virtual memory size (VmSize) weren't helping developers who tried to know how much memory their programs were using.[4]

See also

[edit]

References

[edit]
  1. Dalmasso, Isabelle; Datta, Soumya Kanti; Bonnet, Christian; Nikaein, Navid (July 2013), "Survey, comparison and evaluation of cross platform mobile application development tools", 2013 9th International Wireless Communications and Mobile Computing Conference (IWCMC), Institute of Electrical & Electronics Engineers (IEEE), pp. 323–328, doi:10.1109/iwcmc.2013.6583580, S2CID 15990920.
  2. Tsiligkos, Kleomenis; Meliones, Apostolos (August 2014), "Formulating Optimized Storage and Memory Space Specifications for Linux Network Embedded Systems", 2014 IEEE International Conference on High Performance Computing and Communications, 6th International Symposium on Cyberspace Safety and Security, and 11th International Conference on Embedded Software and Syst (HPCC, CSS, ICESS), Institute of Electrical & Electronics Engineers (IEEE), pp. 580–584, doi:10.1109/hpcc.2014.99, S2CID 9689524.
  3. Mackall, Matt (2009), "smem: understanding memory usage" (PDF), Embedded Linux Conference.
  4. corbet (April 18, 2007), ELC: How much memory are applications really using?, LWN.net, retrieved 2016-03-17.