The operation will run in a single anti-compaction thread so it won't
consume more than 1 CPU. The operation will mostly be IO-bound with the
disk being the most bottleneck. Are running it on a direct-attached SSD? It
won't perform well if you're running it on an EBS volume or some other slow
disk.
Hi folks,
I'm running a job on an offline node to test how long it takes to run
sstablesplit several large sstable.
I'm a bit dismayed to see it took about 22 hours to process a 1.5
gigabyte sstable! I worry about the 32 gigabyte sstable that is my
ultimate target to split.
This is running on a
