|
|
| (22 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt) |
| Zeile 1: |
Zeile 1: |
| − | {{BenutzerSeitenNichtVeraendernWarnung|rdiez}}
| + | #REDIRECT [[Benutzer:Rdiez/PageRemoved]] |
| − | | + | |
| − | = Linux zram =
| + | |
| − | | + | |
| − | [http://en.wikipedia.org/wiki/Zram zram] is a Linux [http://en.wikipedia.org/wiki/Block_device#BLOCKDEV block device] that lives in RAM and compresses any data written to it.
| + | |
| − | | + | |
| − | When created, a zram device advertises its nominal capacity as empty space but allocates no actual memory. You can then create a filesystem on the zram device and use it as a [http://en.wikipedia.org/wiki/Ram_disk RAM disk]. As data is gradually written to it, zram will allocate as much kernel memory as necessary to hold the compressed data.
| + | |
| − | | + | |
| − | Compressing data takes CPU time, but can be faster than writing to a physical hard disk. If the data happens to not compress well, zram will allocate as much RAM as all the original data. If that is always the case, then it is best to use an uncompressed RAM disk like ''ramdisk'', ''ramfs'' or ''tmpfs''.
| + | |
| − | | + | |
| − | zram does not support the [http://en.wikipedia.org/wiki/TRIM TRIM command], which is typically used with [http://en.wikipedia.org/wiki/Ssd SSD disks]. Therefore, zram will not free allocated memory even if all files are deleted. It's a little weird, because zram's predecessor project [https://code.google.com/p/compcache/ compcache] does have this feature.
| + | |
| − | | + | |
| − | == Availability ==
| + | |
| − | | + | |
| − | zram was considered stable as of Linux kernel version 3.14, released in March 2014. Ubuntu 14.04 has kernel version 3.13 and its zram is still considered experimental, although it had already enjoyed widespread usage then.
| + | |
| − | | + | |
| − | The version planned for kernel 3.15 supports the alternative compression algorithm [http://en.wikipedia.org/wiki/LZ4_%28compression_algorithm%29 LZ4], in addition to the default [http://en.wikipedia.org/wiki/Lzo LZO]. zram does NOT attempt to recompress the data in the background if the CPU is idle.
| + | |
| − | | + | |
| − | == Using zram as Swap Device ==
| + | |
| − | | + | |
| − | Using zram as a swap device is an interesting idea. I have not found on the Internet many performance tests yet, but most people who have tried it report an increased performance for standard office tasks, especially if the computer has little RAM. That seems like a contradiction at first, because zram uses RAM itself, making a scarce resource even scarcer.
| + | |
| − | | + | |
| − | A typical compression ratio for a zram swap file, taking all the management overhead into consideration, is factor 2.5 (data gets compressed to a 40% of the original size).
| + | |
| − | | + | |
| − | zram can be used in embedded devices without any storage device for a standard swap file. This way, the virtual memory size can be somewhat larger than the RAM size.
| + | |
| − | | + | |
| − | === Alternative ===
| + | |
| − | | + | |
| − | [http://en.wikipedia.org/wiki/Zswap zswap] takes the cache approach instead, so it always needs a swap device underneath. It is more flexible, as it can dynamically cache any part of the swap file, no matter how much RAM the computer has. Ubuntu's 14.04 stock kernel does not support ''zswap''.
| + | |
