scylladb

mirror of https://github.com/scylladb/scylladb.git synced 2026-04-19 16:15:07 +00:00

Files

Glauber Costa 70a89ab4ab compaction: do not assume I/O priority class

We shouldn't assume the I/O priority class for compactions.  For
instance, if we are dealing with offstrategy compactions we may want to
use the maintenance group priority for them.

For now, all compactions are put in the compaction class.  rewrite
compactions (scrub, cleanup) could be maintenance, but we don't have
clear access to the database object at this time to derive the
equivalent CPU priority. This is planned to be changed in the future,
and when we do change it, we'll adjust.

Same goes for resharding: while we could at this point change it we'd
risking memory pressure since resharding is run online and sstables are
shared until resharding is done. When we move it to offline execution
we'll do it with maintenance priority.

Signed-off-by: Glauber Costa <glauber@scylladb.com>
Message-Id: <20200512002233.306538-3-glauber@scylladb.com>

2020-05-12 08:23:19 +03:00

memory_footprint_test.cc

test: memory_footprint: Avoid invalid identifiers as columnnames

2020-05-07 17:33:34 +03:00

perf_cache_eviction.cc

everywhere: Use uninitialized_string instead of sstring::initialized_later

2020-03-10 13:17:49 -07:00

perf_checksum.cc

tests: move all test source files to their new locations

2019-12-16 17:47:42 +03:00

perf_cql_parser.cc

everywhere: Don't assume sstring::begin() and sstring::end() are pointers