. Now it is clear that what are some benefits of this
> patch. I will send it for review once it is ready and hopefully it gets
> accepted.
>
>
>
> Thanks,
>
> Amit
>
>
>
> *From:* Bowen Song via dev
> *Sent:* Tuesday, July 26, 2022 5:36 PM
> *To:* dev@cassand
: [DISCUSS] Improve Commitlog write path
[CAUTION: External Email]
Hi Amit,
That's some brilliant tests you have done there. It shows that the compaction
throughput not only can be a bottleneck on the speed of insert operations, but
it can also stress the JVM garbage collector. As a result
long. With
lower throughput large system can ingest more data. Does it make sense ?
Thanks,
Amit
*From:* Bowen Song via dev
*Sent:* Friday, July 22, 2022 4:37 PM
*To:* dev@cassandra.apache.org
*Subject:* Re: [DISCUSS] Improve Commitlog write path
[CAUTION: External Email]
Hi Amit
beneficial for workloads where
data is not kept/left on nodes for too long. With lower throughput large system
can ingest more data. Does it make sense ?
Thanks,
Amit
From: Bowen Song via dev
Sent: Friday, July 22, 2022 4:37 PM
To: dev@cassandra.apache.org
Subject: Re: [DISCUSS] Improve Commitlog write path
022 10:24 PM
> *To:* dev@cassandra.apache.org
> *Cc:* Bowen Song ; Raghavendra, Prakash <
> prakash.raghaven...@amd.com>
> *Subject:* Re: [DISCUSS] Improve Commitlog write path
>
>
>
> [CAUTION: External Email]
>
> Amit, welcome and thank you for contribut
Subject: Re: [DISCUSS] Improve Commitlog write path
[CAUTION: External Email]
Amit, welcome and thank you for contributing the results from your test and
opening this discussion.
I don’t think anyone is arguing that the database shouldn’t take advantage of
available hardware.
A few things
:56 PM
To: dev@cassandra.apache.org
Cc: Bowen Song ; Raghavendra, Prakash
Subject: Re: [DISCUSS] Improve Commitlog write path
[CAUTION: External Email]
Hi Amit,
I am inclined to agree with Bowen Song, in that benchmarks from an initially empty cluster tend to lean more heavily
: [DISCUSS] Improve Commitlog write path
[CAUTION: External Email]
Hi Amit,
I am inclined to agree with Bowen Song, in that benchmarks from an initially
empty cluster tend to lean more heavily on memtable and commit log bottlenecks
than a real-world long running cluster does, as the algorithmic
;
>
> Thanks,
>
> Amit
>
>
>
> *From:* Bowen Song via dev
> *Sent:* Wednesday, July 20, 2022 4:13 PM
> *To:* dev@cassandra.apache.org
> *Subject:* Re: [DISCUSS] Improve Commitlog write path
>
>
>
> [CAUTION: External Email]
>
> From my past exp
ti-threading is good to have now ? else please suggest
if I need to test further.
Thanks,
Amit
*From:* Bowen Song via dev
*Sent:* Wednesday, July 20, 2022 4:13 PM
*To:* dev@cassandra.apache.org
*Subject:* Re: [DISCUSS] Improve Commitlog write path
[CAUTION: External Email]
From my past experi
rom: Bowen Song via dev
> Sent: Wednesday, July 20, 2022 4:13 PM
> To: dev@cassandra.apache.org
> Subject: Re: [DISCUSS] Improve Commitlog write path
>
> [CAUTION: External Email]
> From my past experience, the bottleneck for insert heavy workload is likely
> to be
to test further.
Thanks,
Amit
From: Bowen Song via dev
Sent: Wednesday, July 20, 2022 4:13 PM
To: dev@cassandra.apache.org
Subject: Re: [DISCUSS] Improve Commitlog write path
[CAUTION: External Email]
>From my past experience, the bottleneck for insert heavy workload is likely to
>be comp
From my past experience, the bottleneck for insert heavy workload is
likely to be compaction, not commit log. You initially may see commit
log as the bottleneck when the table size is relatively small, but as
the table size increases, compaction will likely take its place and
become the new
[Public]
Hi all,
(My previous mail is not appearing in mailing list and resending again after 2
days)
Myself Amit and working at AMD Bangalore, India. I am new to Cassandra and need
to do Cassandra testing on large core systems. Usually should test on
multi-nodes Cassandra but started with
14 matches
Mail list logo
