16 05:44
> *To:* user@cassandra.apache.org
> *Subject:* Re: Are Cassandra writes are faster than reads?
>
> They can be and it depends on your compaction strategy :)
>
> On Sun, 6 Nov 2016 at 21:24 Ali Akhtar <ali.rac...@gmail.com
> <http://redir.aspx?REF=KvuN_F91CkILmAKkPOD8RL
@cassandra.apache.org
Subject: Re: Are Cassandra writes are faster than reads?
They can be and it depends on your compaction strategy :)
On Sun, 6 Nov 2016 at 21:24 Ali Akhtar
<ali.rac...@gmail.com<redir.aspx?REF=KvuN_F91CkILmAKkPOD8RLOkpaObm4vWZ4CTx2PNAjG8Cvd6wAfUCAFtYWlsdG86YWxpLnJhYzIwMEBnbWFpb
]
Sent: 07 November 2016 10:43
To: user@cassandra.apache.org
Subject: Re: Are Cassandra writes are faster than reads?
Thanks Jeff and Ben for the info.
On Mon, Nov 7, 2016 at 6:44 AM, Ben Bromhead
<b...@instaclustr.com<redir.as
Thanks Jeff and Ben for the info.
On Mon, Nov 7, 2016 at 6:44 AM, Ben Bromhead wrote:
> They can be and it depends on your compaction strategy :)
>
> On Sun, 6 Nov 2016 at 21:24 Ali Akhtar wrote:
>
>> tl;dr? I just want to know if updates are bad for
They can be and it depends on your compaction strategy :)
On Sun, 6 Nov 2016 at 21:24 Ali Akhtar wrote:
> tl;dr? I just want to know if updates are bad for performance, and if so,
> for how long.
>
> On Mon, Nov 7, 2016 at 10:23 AM, Ben Bromhead
tl;dr? I just want to know if updates are bad for performance, and if so,
for how long.
On Mon, Nov 7, 2016 at 10:23 AM, Ben Bromhead wrote:
> Check out https://wiki.apache.org/cassandra/WritePathForUsers for the
> full gory details.
>
> On Sun, 6 Nov 2016 at 21:09 Ali
Check out https://wiki.apache.org/cassandra/WritePathForUsers for the full
gory details.
On Sun, 6 Nov 2016 at 21:09 Ali Akhtar wrote:
> How long does it take for updates to get merged / compacted into the main
> data file?
>
> On Mon, Nov 7, 2016 at 5:31 AM, Ben Bromhead
How long does it take for updates to get merged / compacted into the main
data file?
On Mon, Nov 7, 2016 at 5:31 AM, Ben Bromhead wrote:
> To add some flavor as to how the commitlog implementation is so quick.
>
> It only flushes to disk every 10s by default. So writes are
To add some flavor as to how the commitlog implementation is so quick.
It only flushes to disk every 10s by default. So writes are effectively
done to memory and then to disk asynchronously later on. This is generally
accepted to be OK, as the write is also going to other nodes.
You can of
Cassandra writes are particularly fast, for a few reasons:
1) Most writes go to a commitlog (append-only file, written linearly, so
particularly fast in terms of disk operations) and then pushed to the memTable.
Memtable is flushed in batches to the permanent data files, so it buffers
10 matches
Mail list logo