Re: Compaction throughput

Thanks! On Friday, July 19, 2019, 10:15:43 PM GMT+3, Jon Haddad wrote: It's a limit on the total compaction throughput.  On Fri, Jul 19, 2019 at 10:39 AM Vlad wrote: Hi, is  'nodetool setcompactionthroughput' sets limit for all compactions on the node, or is it per compaction

Re: Compaction throughput

It's a limit on the total compaction throughput. On Fri, Jul 19, 2019 at 10:39 AM Vlad wrote: > Hi, > > is 'nodetool setcompactionthroughput' sets limit for all compactions on > the node, or is it per compaction thread? > > Thanks. >

Compaction throughput

Hi, is  'nodetool setcompactionthroughput' sets limit for all compactions on the node, or is it per compaction thread? Thanks.

Re: Compaction throughput vs. number of compaction threads?

Hi, The compaction throughput is indeed shared by all compactors. I would not advise to go below 8MB/s per compactor as slowing down compactions put more pressure on the heap. When tuning compaction, the first thing to do is evaluate the maximum throughput your disks can sustain without

Compaction throughput vs. number of compaction threads?

Hello, most likely obvious and perhaps already answered in the past, but just want to be sure ... E.g. I have set: concurrent_compactors: 4 compaction_throughput_mb_per_sec: 16 I guess this will lead to ~ 4MB/s per Thread if I have 4 compactions running in parallel? So, in case of upscaling

Re: compaction throughput

re. So I guess I should've asked the question more clearly: 1. Is ~25 M/s a reasonable compaction throughput for one core? 2. Is there any configuration that affects single core compaction throughput? 3. Is concurrent_compactors the

Re: compaction throughput

gt;> >> 2016-01-16 0:18 GMT+01:00 Kai Wang <dep...@gmail.com>: >> >>> Jeff & Sebastian, >>> >>> Thanks for the reply. There are 12 cores but in my case C* only uses one >>> core most of the time. *nodetool compactionstats* shows there's only &g

Re: compaction throughput

res but in my case C* only uses one core most of the time. nodetool compactionstats shows there's only one compactor running. I can see C* process only uses one core. So I guess I should've asked the question more clearly: 1. Is ~25 M/s a reasonable compaction throughput for one core? 2. Is the

Re: compaction throughput

FDF2> >>> >>> 2016-01-16 0:18 GMT+01:00 Kai Wang <dep...@gmail.com>: >>> >>>> Jeff & Sebastian, >>>> >>>> Thanks for the reply. There are 12 cores but in my case C* only uses >>>> one core most of the time.

Re: compaction throughput

s for the reply. There are 12 cores but in my case C* only uses one >> core most of the time. *nodetool compactionstats* shows there's only one >> compactor running. I can see C* process only uses one core. So I guess I >> should've asked the question more clearly: >&

Re: compaction throughput

com >>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> >>>> <#-1919795192_-2069969251_1162782367_-1582318301_DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>>> >>>> 2016-01-16 0:18 GMT+01:00 Kai W

compaction throughput

Hi, I am trying to figure out the bottleneck of compaction on my node. The node is CentOS 7 and has SSDs installed. The table is configured to use LCS. Here is my compaction related configs in cassandra.yaml: compaction_throughput_mb_per_sec: 160 concurrent_compactors: 4 I insert about 10G of

Re: compaction throughput

I forget to mention I am using C* 2.2.4 On Jan 15, 2016 3:53 PM, "Kai Wang" wrote: > Hi, > > I am trying to figure out the bottleneck of compaction on my node. The > node is CentOS 7 and has SSDs installed. The table is configured to use > LCS. Here is my compaction related

Re: compaction throughput

Compaction is generally CPU bound and relatively slow. Exactly why that is I’m uncertain. > On Jan 15, 2016, at 12:53 PM, Kai Wang wrote: > > Hi, > > I am trying to figure out the bottleneck of compaction on my node. The node > is CentOS 7 and has SSDs installed. The table

Re: compaction throughput

*nodetool setcompactionthroughput 0* Will only affect future compactions, not the ones that are currently running. All the best, [image: datastax_logo.png] Sebastián Estévez Solutions Architect | 954 905 8615 | sebastian.este...@datastax.com [image: linkedin.png]

Re: compaction throughput

With SSDs, the typical recommendation is up to 0.8-1 compactor per core (depending on other load). How many CPU cores do you have? From: Kai Wang Reply-To: "user@cassandra.apache.org" Date: Friday, January 15, 2016 at 12:53 PM To: "user@cassandra.apache.org" Subject: c

Re: compaction throughput

M/s a reasonable compaction throughput for one core? 2. Is there any configuration that affects single core compaction throughput? 3. Is concurrent_compactors the only option to parallelize compaction? If so, I guess it's the compaction strategy itself that decides when to parallelize and when to b

Re: compaction throughput

s for the reply. There are 12 cores but in my case C* only uses one > core most of the time. *nodetool compactionstats* shows there's only one > compactor running. I can see C* process only uses one core. So I guess I > should've asked the question more clearly: > > 1. Is ~25 M/s a r

Re: compaction throughput

& Sebastian, >>> >>> Thanks for the reply. There are 12 cores but in my case C* only uses one >>> core most of the time. *nodetool compactionstats* shows there's only >>> one compactor running. I can see C* process only uses one core. So I guess >>>

Re: compaction throughput

> core most of the time. *nodetool compactionstats* shows there's only one >> compactor running. I can see C* process only uses one core. So I guess I >> should've asked the question more clearly: >> >> 1. Is ~25 M/s a reasonable compaction throughput for one core? >>

RE: compaction throughput rate not even close to 16MB

: Hiller, Dean [mailto:dean.hil...@nrel.gov] Sent: Wednesday, April 24, 2013 23:38 To: user@cassandra.apache.org Subject: Re: compaction throughput rate not even close to 16MB Thanks much!!! Better to hear at least one other person sees the same thing ;). Sometimes these posts just go silent

compaction throughput rate not even close to 16MB

I was wondering about the compactionthroughput. I never see ours get even close to 16MB and I thought this is supposed to throttle compaction, right? Ours is constantly less than 3MB/sec from looking at our logs or do I have this totally wrong? How can I see the real throughput so that I can

Re: compaction throughput rate not even close to 16MB

I have noticed the same. I think in the real world your compaction throughput is limited by other things. If I had to speculate I would say that compaction can remove expired tombstones, however doing this requires bloom filter checks, etc. I think that setting is more important with multi

Re: compaction throughput rate not even close to 16MB

On Wed, Apr 24, 2013 at 1:33 PM, Edward Capriolo edlinuxg...@gmail.com wrote: I think that setting is more important with multi threaded compaction and/or more compaction slots. In those cases it may actually throttle something. Or if you're simultaneously doing a repair, which does a

Re: compaction throughput rate not even close to 16MB

@cassandra.apache.orgmailto:user@cassandra.apache.org Date: Wednesday, April 24, 2013 2:33 PM To: user@cassandra.apache.orgmailto:user@cassandra.apache.org user@cassandra.apache.orgmailto:user@cassandra.apache.org Subject: Re: compaction throughput rate not even close to 16MB I have noticed the same. I think in the real

Re: compaction throughput rate not even close to 16MB

, we are on SSD. -Wei From: Hiller, Dean dean.hil...@nrel.gov To: user@cassandra.apache.org user@cassandra.apache.org Sent: Wednesday, April 24, 2013 1:37 PM Subject: Re: compaction throughput rate not even close to 16MB Thanks much!!!  Better to hear at least