Comments for Streamy Development Blog

Comment on CAP Theorem by HBase vs. Cassandra: NoSQL Battle! | Road to Failure

HBase vs. Cassandra: NoSQL Battle! | Road to Failure — Thu, 29 Oct 2009 19:42:49 +0000

[...] This article at Streamy explains CAP theorem (Consistency, Availability, Partitioning) and how the BigTable-derived HBase and the Dynamo-derived Cassandra differ. [...]

Comment on CAP Theorem by Insights on Parallel and Distributed Systems « Metaphysical Developer

Insights on Parallel and Distributed Systems « Metaphysical Developer — Tue, 01 Sep 2009 01:31:45 +0000

[...] CAP Theorem: This has to do with distributed programming only, and many people said a lot of about this. But essentially it means that a distributed system can only have at most two [...]

Comment on Web Scale by Insights on Parallel and Distributed Systems « Metaphysical Developer

Insights on Parallel and Distributed Systems « Metaphysical Developer — Tue, 01 Sep 2009 01:12:15 +0000

[...] 31, 2009 in Uncategorized At least two trends are making paralell and distributed programming come to focus: computers with multiple cores [...]

Comment on CAP Theorem by CAP Theorem « Spoot!

CAP Theorem « Spoot! — Fri, 28 Aug 2009 10:16:08 +0000

[...] Posted in distributed computing by nbonvin on August 28, 2009 Nice introduction about the CAP (Consistency, Availability, Partition) theorem. Tagged with: availability, CAP [...]

Comment on HOWTO: Determine the size of a Java Object or Class by Doug Clayton

Doug Clayton — Tue, 25 Aug 2009 17:48:11 +0000

Shen,

The instance of TestClass itself has 8 bytes of overhead. That has to contain at least one reference to point to the class object for that instance. Based on my tests, the other 4 hold some value, because the overhead is 16 bytes on a 64-bit JVM, rather than 8 as it would be if those 4 bytes were just padding.

In your example, the 4 bytes taken up by the “in” reference are allocated on the stack, not on the heap. Also, the “this” implicit reference is also allocated on the stack: it’s passed to methods just like any parameter, but it’s just hidden.

Comment on HOWTO: Determine the size of a Java Object or Class by Doug Clayton

Doug Clayton — Tue, 25 Aug 2009 17:34:16 +0000

The reason everything is aligned to 8-byte boundaries is because most processors won’t let you access an 8-byte value unless it is aligned to 8 bytes. Since the longest primitive Java supports is 8 bytes (double, long, or reference in 64 bit), it aligns its objects to that so that any object can be placed to any valid location in memory without worrying about whether it has a long or double inside it that can handle the resulting alignment. It just has to make sure that the long or double is aligned properly to the top of the object, and that guarantees it will be aligned in memory for the processor.

Comment on CAP Theorem by Dom

Dom — Tue, 25 Aug 2009 02:06:25 +0000

So thats what you guys are talking about all the time…I got it.

Comment on HUG7: HBase User Group Wrap-Up by Jonathan Gray

Jonathan Gray — Thu, 13 Aug 2009 21:07:56 +0000

Hey Otis. Responded to your post over on your blog:

http://www.jroller.com/otis/entry/hbase_vs_rdbms_star_schema

Comment on HUG7: HBase User Group Wrap-Up by Otis Gospodnetic

Otis Gospodnetic — Wed, 12 Aug 2009 18:00:13 +0000

I’m curious about using HBase for analytics. Why HBase for analytics vs. a star schema with dimensions, etc. in RDBMS?

This is not a tease question!

Comment on HUG7: HBase User Group Wrap-Up by stack

stack — Wed, 12 Aug 2009 05:11:01 +0000

Here’s some pictures: http://picasaweb.google.com/saint.ack/HbaseHackathon#