https://bugs.kde.org/show_bug.cgi?id=367941
Bug ID: 367941
Summary: Each keystroke generates a disk write
Product: kate
Version: 3.14.2
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: kdebts8...@iceteks.com
As title, each keystroke generates disk I/O, it writes to a .*.kate-swp file
where * is the file name. This causes typing in Kate to be very slow if the
file is located on a network and if the network is experiencing any kind of
latency (ex: VPN over internet or backup jobs happening). There is an option
under "Configure Kate, Open/Save, advanced" called "Disable swap file syncing"
which I presume is to disable this feature, but whether the option is on or
not, it still does it.
I read previous bug reports and they were closed as this being by design. If
that's the case, can you please add another option to disable this completely
and force the data to be in memory and only save when the save button is set?
Optionally add an option to just have the swap file somewhere else, such as a
local directory. (this would kill SSDs though... maybe a local ram disk?) This
issue makes Kate unusable over a network. It is nice to store files over a SMB
or NFS volume and work on them directly while they are on a central file server
that uses raid, has backups etc while not having to worry about doing any of
that at the client level.
How to reproduce: open a file that is stored on a NFS server, create a high
load on that server, such as a dd operation on the same raid array. Hold down
a key. It will be extremely choppy. Optionally a packet sniffer can be used to
confirm many NFS writes while the key is being held down.
--
You are receiving this mail because:
You are watching all bug changes.
