Got it, thanks for clearing things up! I guess setting cache_type to
'none' does the trick for now (albeit incurring a higher query latency).
On Wed, Jul 22, 2015 at 12:25 AM Mattias Persson
wrote:
> On Tue, Jul 21, 2015 at 10:27 PM, Zongheng Yang
> wrote:
>
>> Thanks, Matthias. If I understa
On Tue, Jul 21, 2015 at 10:27 PM, Zongheng Yang
wrote:
> Thanks, Matthias. If I understand you correctly, the result of my
> previous *2 calculation roughly matching the two store files on disk is not
> due to JVM String overhead, rather it is due to Neo4j's quantization
> overhead.
>
> There's
Thanks, Matthias. If I understand you correctly, the result of my previous
*2 calculation roughly matching the two store files on disk is not due to
JVM String overhead, rather it is due to Neo4j's quantization overhead.
There's one loose end that I wish to tighten: why does ~27GB of string
chara
To clarify, it's not serialized String objects. Neo4j stores the character
data, either compacted by being able to use a smaller charset than
utf-8/ascii so that fewer bits per character is required, or if string is
"long" by neo4j measures, as plain characters into the
neostore.propertystore.d
If those are serialized String objects then I'm seeing the following
mismatch between measurement and calculation:
The graph I'm using has 4.9 million nodes, each of which has 40 string
properties (each of which has 16 characters). It has 70 million directed
edges, each of which has 1 string prop
> Does this sound right? Also, node properties & relationship properties are
> interleaved and stored together in these files, right?
Yes and yes.
> Lastly -- is everything in (1) and (2) deserialized JVM objects in raw bytes
> *or* just UTF-8 characters? It could make a difference, since if
Thanks! Some follow-ups: my current understanding is that,
(1) propertystore.db: metadata (as you mentioned) + possibly inlined short
strings/fields [otherwise, pointers]
(2) propertystore.db.strings: long string properties
Does this sound right? Also, node properties & relationship propertie
The propertystore.db file also has metadata about which entities a property
belongs to, what the property names are, what type the value of a property has,
and where to find the property values in cases where those are stored in other
files such as propertystore.db.strings.
--
Chris Vest
System
Hi all,
Quick question: what do propertystore.db and propertystore.db.strings
store, respectively?
My CSV headers look like these:
edges -- :START_ID, :END_ID, :TYPE, timestamp:LONG, attr
nodes -- :ID, name0, ..., name39
And propertystore.db totals 10GB, propertystore.db.strings totals 17GB.
