Commit a36fbeb
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -5,6 +5,12 @@ When reading from many possibly large files in a fashion similar to random acces | |||
| 5 | 5 | Although memory maps have many advantages, they represent a very limited system resource as every map uses one file descriptor, whose amount is limited per process. On 32 bit systems, the amount of memory you can have mapped at a time is naturally limited to theoretical 4GB of memory, which may not be enough for some applications. | |
| 6 | 6 | ||
| 7 | 7 | ||
| 8 | + ## Limitations | ||
| 9 | + | ||
| 10 | + * **System resources (file-handles) are likely to be leaked!** This is due to the library authors reliance on a deterministic `__del__()` destructor. | ||
| 11 | + * The memory access is read-only by design. | ||
| 12 | + * In python below 2.6, memory maps will be created in compatibility mode which works, but creates inefficient memory mappings as they always start at offset 0. | ||
| 13 | + | ||
| 8 | 14 | ||
| 9 | 15 | ## Overview | |
| 10 | 16 | ||
@@ -33,11 +39,6 @@ For performance critical 64 bit applications, a simplified version of memory map | |||
| 33 | 39 | ||
| 34 | 40 | The package was tested on all of the previously mentioned configurations. | |
| 35 | 41 | ||
| 36 | - ## Limitations | ||
| 37 | - | ||
| 38 | - * The memory access is read-only by design. | ||
| 39 | - * In python below 2.6, memory maps will be created in compatibility mode which works, but creates inefficient memory mappings as they always start at offset 0. | ||
| 40 | - | ||
| 41 | 42 | ## Installing smmap | |
| 42 | 43 | ||
| 43 | 44 | [](https://readthedocs.org/projects/smmap/?badge=latest) | |
0 commit comments