#1728 mod_tombstone: inefficient I/O with internal storage
What steps will reproduce the problem?
1. Use mod_storage_internal (default)
2. Enable mod_tombstones on a busy server
What is the expected output?
The server should function normally.
What do you see instead?
Prosody consumes a lot of CPU/IO. This is caused by mod_tombstones using a map store, and checking it on almost every presence stanza.
Although adding storage access on every presence stanza will degrade performance for SQL, map stores are particularly inefficient with internal storage (where a shim is used that loads the entire tombstone list to retrieve a single key).
What version of the product are you using? On what operating system?
Please provide any additional information below.