Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Importance of a Data Format Part 5 — The End Result

DZone's Guide to

The Importance of a Data Format Part 5 — The End Result

What the blittable format gives us is immediate access to any property without the need to parse the whole thing. How important is that for us? Read on to learn more.

· Database Zone
Free Resource

Read why times series is the fastest growing database category.

So far, I have written about the problem we had, the requirement for the solution, then did a deep dive into the actual implementation, and finally I talked about the improvement in performance, which was a nice double digits improvement in percentage. There are a couple of tricks there that I still want to talk about, but that is pretty much it.

Except that this actually misses the entire point of this exercise. What the blittable format gives us is immediate access to any property without the need to parse the whole thing. How important is that for us?

Well, for one specific scenario, that is actually quite important. Let us imagine that we have the following RavenDB index:

from c in docs.Companies
select new
{
c.Name,
c.Overview
}

Here are the results, counting purely the time to load about 18,000 documents and get the relevant data:

image

I removed all I/O from the benchmark, and I'm testing only the cost of loading documents already saved in RavenDB and getting those properties from them.

And, that is what I'm talking about! 

Learn how to get 20x more performance than Elastic by moving to a Time Series database.

Topics:
data format ,data access object ,ravendb performance ,json

Published at DZone with permission of Oren Eini, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}