This HTML5 document contains 20 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
dctermshttp://purl.org/dc/terms/
dbohttp://dbpedia.org/ontology/
foafhttp://xmlns.com/foaf/0.1/
n5https://global.dbpedia.org/id/
dbthttp://dbpedia.org/resource/Template:
rdfshttp://www.w3.org/2000/01/rdf-schema#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
wikipedia-enhttp://en.wikipedia.org/wiki/
dbphttp://dbpedia.org/property/
provhttp://www.w3.org/ns/prov#
dbchttp://dbpedia.org/resource/Category:
xsdhhttp://www.w3.org/2001/XMLSchema#
goldhttp://purl.org/linguistics/gold/
wikidatahttp://www.wikidata.org/entity/
dbrhttp://dbpedia.org/resource/

Statements

Subject Item
dbr:Unique_set_size
rdf:type
dbo:AnatomicalStructure
rdfs:label
Unique set size
rdfs:comment
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. This concept is used for software running under the Linux operating system. It was proposed by Matt Mackall because of the complications that arose when trying to count the "real memory" used by a process. 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.
dcterms:subject
dbc:Memory_management
dbo:wikiPageID
49596175
dbo:wikiPageRevisionID
991255919
dbo:wikiPageWikiLink
dbr:Linux dbc:Memory_management dbr:Resident_set_size dbr:Proportional_set_size dbr:RAM dbr:Virtual_memory
owl:sameAs
n5:2Nu58 wikidata:Q25313283
dbp:wikiPageUsesTemplate
dbt:Reflist
dbo:abstract
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. This concept is used for software running under the Linux operating system. It was proposed by Matt Mackall because of the complications that arose when trying to count the "real memory" used by a process. 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.
gold:hypernym
dbr:Portion
prov:wasDerivedFrom
wikipedia-en:Unique_set_size?oldid=991255919&ns=0
dbo:wikiPageLength
2275
foaf:isPrimaryTopicOf
wikipedia-en:Unique_set_size