Reference counting happens at run time, not compile time. It's not free
either. Every time a reference is added, there's overhead in tracking it.
It also doesn't catch cycles. You still need garbage collection to avoid
memory leaks.
On Sun, Nov 27, 2016 at 12:31 AM Benjamin Roth
Maybe I was not totally clear. Reference counting is of course done at
runtime but the compiler automates where + when to do the counting.
Before, the developer had to retain + release objects manually. Since ARC,
this is done by the compiler at file level.
Nothing is "free" in this world. There
Thanks Ben and Hiro,
I've reported it at https://issues.apache.org/jira/browse/CASSANDRA-12960.
I'll use `truncatehints` or DROP command after this.
On Sun, Nov 27, 2016 at 12:33 PM, Ben Slater
wrote:
> By “undocumented limitation”, I meant “TRUNCATE” is mainly
Hi @Kant Kodali,
We have multiple clusters running zing .
One cluster has 11/11 and another one also has 11/11.(190 GB mem,6TB hard disk
and 16 Physical core machines)
The average read size is around 200KB and it can go upto 6 MB.
We are using g1GC in most clusters with 26GB heap and extra
Hi Hari
Could you share your G1GC settings please?
On Sun, Nov 27, 2016 at 9:57 PM, Harikrishnan Pillai <
hpil...@walmartlabs.com> wrote:
> Hi @Kant Kodali,
>
> We have multiple clusters running zing .
>
> One cluster has 11/11 and another one also has 11/11.(190 GB mem,6TB hard
> disk and 16
Hi All,
I am able to read cdc events from key spaces like *system *and
*system_schema,
*but not from the one that I created. Any help on this?.
Thanks & Regards
Kamesh.
On Wed, Nov 23, 2016 at 9:14 PM, Kamesh wrote:
> Hi Carlos,
> durable_writes = true.
>
>
Hi All,
We have 2 Cassandra DC with below config:
DC1: In DC1 we have 9 Servers with 64 GB ram 40 Core machines. In this DC we
have Cassandra version: 2.1.4. And We have 2 TB data on each server.
Application is connected with DC.
DC2: In DC2 we have 5 Servers with 64 GB ram 40 Core machines.
Yes I am well aware of Scyalldb. It might be well written in C++ but the
performance gain they are claiming has very little to do with moving from
Java to C++. They had major design changes such as moving away from SEDA to
TPC and so on. Moreover I would say it still needs to mature. Lot of users
I didn't even know there are plans to move to TPC in Cs. Thanks for that
update. After all I will follow the development of both Scylla and Cs and
am excited about the future of both!
Am 27.11.2016 10:02 schrieb "Kant Kodali" :
> Yes I am well aware of Scyalldb. It might be