Unit Instance

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "translation": "https://translate-dev.freebsd.org/api/translations/documentation/articlesvm-design_index/en/?format=api",
    "source": [
        "We will end with the page coloring optimizations.  Page coloring is a performance optimization designed to ensure that accesses to contiguous pages in virtual memory make the best use of the processor cache.  In ancient times (i.e. 10+ years ago) processor caches tended to map virtual memory rather than physical memory.  This led to a huge number of problems including having to clear the cache on every context switch in some cases, and problems with data aliasing in the cache.  Modern processor caches map physical memory precisely to solve those problems.  This means that two side-by-side pages in a processes address space may not correspond to two side-by-side pages in the cache.  In fact, if you are not careful side-by-side pages in virtual memory could wind up using the same page in the processor cache-leading to cacheable data being thrown away prematurely and reducing CPU performance.  This is true even with multi-way set-associative caches (though the effect is mitigated somewhat)."
    ],
    "previous_source": "",
    "target": [
        "We will end with the page coloring optimizations.  Page coloring is a performance optimization designed to ensure that accesses to contiguous pages in virtual memory make the best use of the processor cache.  In ancient times (i.e. 10+ years ago) processor caches tended to map virtual memory rather than physical memory.  This led to a huge number of problems including having to clear the cache on every context switch in some cases, and problems with data aliasing in the cache.  Modern processor caches map physical memory precisely to solve those problems.  This means that two side-by-side pages in a processes address space may not correspond to two side-by-side pages in the cache.  In fact, if you are not careful side-by-side pages in virtual memory could wind up using the same page in the processor cache-leading to cacheable data being thrown away prematurely and reducing CPU performance.  This is true even with multi-way set-associative caches (though the effect is mitigated somewhat)."
    ],
    "id_hash": 5700219517434259076,
    "content_hash": 5700219517434259076,
    "location": "documentation/content/en/articles/vm-design/_index.adoc:297",
    "context": "",
    "note": "type: Plain text",
    "flags": "",
    "labels": [],
    "state": 100,
    "fuzzy": false,
    "translated": true,
    "approved": false,
    "position": 61,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 160,
    "source_unit": "https://translate-dev.freebsd.org/api/units/615425/?format=api",
    "priority": 100,
    "id": 615425,
    "web_url": "https://translate-dev.freebsd.org/translate/documentation/articlesvm-design_index/en/?checksum=cf1b3f73366ae684",
    "url": "https://translate-dev.freebsd.org/api/units/615425/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2021-03-20T20:43:35.770698Z"
}