Great, so maybe neo4j-index should be updated to depend on Lucene 2.9.3.
2010/7/9 Bill Janssen jans...@parc.com
Note that a couple of memory issues are fixed in Lucene 2.9.3. Leaking
when indexing big docs, and indolent reclamation of space from the
FieldCache.
Bill
Arijit Mukherjee
Hi,
I have a GraphDB with the following attributes:
Number of nodes: 3.6M
Number of relation types: 2
Total size of DB: 9GB
lucene : 160MB
neostore.nodestore.db : 31MB
neostore.propertystore.db : 2GB
neostore.propertystore.db.strings : 4GB
neostore.relationshipstore.db : 1.5GB
Hi Amir,
I'm just starting with neo4j, but saw some issues with your code from a
normal java-standpoint. Please note, some of them are just
micro-optimizations that may not matter much. But a lot of them are in
your critical path, so perhaps they're worth a look.
On 10-7-2010 17:59 Amir
Are you using kernel/index version 1.0? Regarding the index lookups (each
lookup in its own separate transaction): I think there's a bug in
neo4j-index 1.0 which causes such a transaction (which contains a call to
index.getNodes) to write stuff to and flush the logical log, which of course
is
hi,
Thanks for the advice, Would it be better to use Amazon S3 or EBS storage to
mount the neo4j database?
thanks
Paddy
On Thu, Jul 8, 2010 at 6:24 AM, Dave butlerdi butle...@gmail.com wrote:
We have just started putting the NK stuff together as they recently moved
to
V4 and it is quite a
also can i load the configurations from the neo4j_config.props file if the
GraphDatabaseService is injected by Spring?
The Configuration Settings wiki outlines the setup as :
MapString,String configuration = EmbeddedGraphDatabase.loadConfigurations(
neo4j_config.props );
GraphDatabaseService
6 matches
Mail list logo