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/freebsd-doc/boooks_handbook/en/?format=api",
    "source": [
        "Checksums make it possible to detect duplicate blocks of data as they are written. With deduplication, the reference count of an existing, identical block is increased, saving storage space. To detect duplicate blocks, a deduplication table (<acronym>DDT</acronym>) is kept in memory. The table contains a list of unique checksums, the location of those blocks, and a reference count. When new data is written, the checksum is calculated and compared to the list. If a match is found, the existing block is used. The <acronym>SHA256</acronym> checksum algorithm is used with deduplication to provide a secure cryptographic hash. Deduplication is tunable. If <literal>dedup</literal> is <literal>on</literal>, then a matching checksum is assumed to mean that the data is identical. If <literal>dedup</literal> is set to <literal>verify</literal>, then the data in the two blocks will be checked byte-for-byte to ensure it is actually identical. If the data is not identical, the hash collision will be noted and the two blocks will be stored separately. Because <acronym>DDT</acronym> must store the hash of each unique block, it consumes a very large amount of memory. A general rule of thumb is 5-6 GB of ram per 1 TB of deduplicated data). In situations where it is not practical to have enough <acronym>RAM</acronym> to keep the entire <acronym>DDT</acronym> in memory, performance will suffer greatly as the <acronym>DDT</acronym> must be read from disk before each new block is written. Deduplication can use <acronym>L2ARC</acronym> to store the <acronym>DDT</acronym>, providing a middle ground between fast system memory and slower disks. Consider using compression instead, which often provides nearly as much space savings without the additional memory requirement."
    ],
    "previous_source": "",
    "target": [
        "Checksums make it possible to detect duplicate blocks of data as they are written. With deduplication, the reference count of an existing, identical block is increased, saving storage space. To detect duplicate blocks, a deduplication table (<acronym>DDT</acronym>) is kept in memory. The table contains a list of unique checksums, the location of those blocks, and a reference count. When new data is written, the checksum is calculated and compared to the list. If a match is found, the existing block is used. The <acronym>SHA256</acronym> checksum algorithm is used with deduplication to provide a secure cryptographic hash. Deduplication is tunable. If <literal>dedup</literal> is <literal>on</literal>, then a matching checksum is assumed to mean that the data is identical. If <literal>dedup</literal> is set to <literal>verify</literal>, then the data in the two blocks will be checked byte-for-byte to ensure it is actually identical. If the data is not identical, the hash collision will be noted and the two blocks will be stored separately. Because <acronym>DDT</acronym> must store the hash of each unique block, it consumes a very large amount of memory. A general rule of thumb is 5-6 GB of ram per 1 TB of deduplicated data). In situations where it is not practical to have enough <acronym>RAM</acronym> to keep the entire <acronym>DDT</acronym> in memory, performance will suffer greatly as the <acronym>DDT</acronym> must be read from disk before each new block is written. Deduplication can use <acronym>L2ARC</acronym> to store the <acronym>DDT</acronym>, providing a middle ground between fast system memory and slower disks. Consider using compression instead, which often provides nearly as much space savings without the additional memory requirement."
    ],
    "id_hash": -1166718213906983232,
    "content_hash": -1166718213906983232,
    "location": "book.translate.xml:43459",
    "context": "",
    "note": "(itstool) path: row/entry",
    "flags": "",
    "labels": [],
    "state": 100,
    "fuzzy": false,
    "translated": true,
    "approved": false,
    "position": 7061,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": true,
    "num_words": 265,
    "source_unit": "https://translate-dev.freebsd.org/api/units/157923/?format=api",
    "priority": 100,
    "id": 157923,
    "web_url": "https://translate-dev.freebsd.org/translate/freebsd-doc/boooks_handbook/en/?checksum=6fcefbf74b1896c0",
    "url": "https://translate-dev.freebsd.org/api/units/157923/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2020-04-18T18:15:42.625481Z"
}