On 26 May 2014, at 16:39, Rio Eduardo <rioeduard...@gmail.com> wrote: > 1. For Memory => Is it because Neo4j stores data in RAM? or are there other > causes?
It caches both on the entity level, and also has a page cache for memory mapped bits of the store files. Transaction states are currently also entirely in ram. Neo4j is also implemented in Java, which needs extra room for the GC to work. This last part about the GC and managed memory is why it would use more memory than an equivalent C implementation. Databases are in general very fond of memory, because they want to do as little IO as they can get away with. > 2. For Disk => Is it because Neo4j store all of relationships? or are there > other causes? The storage format is fairly compact for what is stored, actually. It is sort of similar to how MyISAM tables are more compact than InnoDB tables. We still need to store the type and direction for relationships, pointers for both end-nodes and pointers for properties. -- Chris Vest System Engineer, Neo Technology [ skype: mr.chrisvest, twitter: chvest ] -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
