understand its implication for the overall
performance, but I think it is not the main cause for the observation.
4. I also tested CL.ONE vs. CL.QUORUM. I am summarizing that part too.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Denormalization
y failed (no host was tried)
>>
>> I repeated the two cases back and forth several times, and the results
>> remained the same.
>>
>> I also observed CPU usage on the 3 Cassandra servers, and they were all
>> much higher for the de-normalized case.
>>
>>
n.
>
>- Why are there so many exceptions in the de-normalized case? I would
>think Cassandra should be able to handle simultaneous accesses to the same
>data. Why are there NO exceptions for the normalized case? I meant that the
>environments for the two cases are b
e with Java Driver?
Or did I do something wrong?
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Denormalization-leads-to-terrible-rather-than-better-Cassandra-performance-I-am-really-puzzled-tp7600561.html
Sent from the cassandra-u...@incubator.a
Date: Sunday, January 27, 2013 6:51 PM
> To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <
> user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
> Subject: Re: Denormalization
>
> When I said that writes were cheap, I was speaking t
@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Denormalization
When I said that writes were cheap, I was speaking that in a normal case people
are making 2-10 inserts what in a relational database might be one. 30K inserts
lo mailto:edlinuxg...@gmail.com
> >>
> Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <
> user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
> Date: Sunday, January 27, 2013 5:50 PM
> To: "user@cassandra.apache.org&l
@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Denormalization
One technique is on the client side you build a tool that takes the even and
produces N mutations. In c* writes are cheap so essentially, re-write
everything on all changes.
One technique is on the client side you build a tool that takes the even
and produces N mutations. In c* writes are cheap so essentially, re-write
everything on all changes.
On Sun, Jan 27, 2013 at 4:03 PM, Fredrik Stigbäck <
fredrik.l.stigb...@sitevision.se> wrote:
> Hi.
> Since denormalized dat
Oh and check out the last pattern "Scalable equals only index" which can allow
you to still have normalized data though the pattern does denormalization just
enough that you can
1. Update just two pieces of info (the users email for instance and the Xref
table email as well).
Things like PlayOrm exist to help you with half and half of denormalized and
normalized data. There are more and more patterns out there of denormalization
and normalization but allowing for scalability still. Here is one patterns page
https://github.com/deanhiller/playorm/wiki/Patterns-Page
urious how applications
> handle and how to think when modelling, since I guess denormalization
> might increase the complexity of the application.
>
> Fredrik
>
> 2013/1/27 Hiller, Dean >:
> > There is a really a mix of denormalization and normalization. It really
>
I don't have a current use-case. I was just curious how applications
handle and how to think when modelling, since I guess denormalization
might increase the complexity of the application.
Fredrik
2013/1/27 Hiller, Dean :
> There is a really a mix of denormalization and normalization. I
There is a really a mix of denormalization and normalization. It really
depends on specific use-cases. To get better help on the email list, a
more specific use case may be appropriate.
Dean
On 1/27/13 2:03 PM, "Fredrik Stigbäck"
wrote:
>Hi.
>Since denormalized data is first-
Hi.
Since denormalized data is first-class citizen in Cassandra, how to
handle updating denormalized data.
E.g. If we have a USER cf with name, email etc. and denormalize user
data into many other CF:s and then
update the information about a user (name, email...). What is the best
way to handle up
15 matches
Mail list logo