| Age | Commit message (Collapse) | Author | Files | Lines |
|
memory mapping the entire file has been benchmarked to be less
efficient than the old implementation (because of more than
doubling page faults).
A lengthy comment has been written to discuss different
implementations of file reading.
|
|
* file must be in primary memory for scintilla
* we cannot write to scintilla's buffer memory directly
* so mapping the file is best: in the best case it is not copied to primary memory and resides in kernel cache
* in any case, mapping to memory is faster than read()ing into primary memory
* copying from mapped virtual memory to scintilla buffer (via SCI_APPENDTEXT) is faster
than copying from primary memory
|
|
* works with/without save-points (i.e. in batch and interactive mode, both were broken)
* improved file-saving performance (avoid buffer gap removal)
* only root can preserve the ownership of a file owned by another user after file saving
|
|
|
|
|
|
|
|
|
|
|