Marc Grue schrieb:
Would it be possible to use the neo4j entitystore in combination with the neo4j 
traversal API directly for faster queries?

I don't think that query time is the problem. See my other post in this thread. I Will measure the performance of the Lucene store to make sure.

Thanks.

-Falko


Cheers,
Marc

On 2011-12-12, at 15.01, Falko Bräutigam wrote:

Hey guys,

I'm working on a geo spatial application using Qi4j to model the domain 
specific parts. I ran into trouble with the performance and memory consumption.

It takes ~30s to load 10.000 entities (consisting of ~100k ValueComposites of 
different types). After loading all this eats up ~100MB of RAM. This is to slow 
and to much.

10K entities are not much for a GIS application. Given the current memory 
foodprint (and 1GB Java heap) not even 10 users can work with the application 
concurrently.

Usually a GIS application works in a pipelined mode when rendering features 
(entities). Memory is never a problem with that architecture. Unfortunatelly 
Qi4j holds all entities of an UoW in memory. We discussed this earlier on this 
list. So I added a cache SPI to UnitOfWorkInstance. This works but it does not 
actually cure the problem of memory consumption because of the time needed to 
re-instantiate the entities.

Any ideas on this would be greatly appreciated.

-Falko
--
Falko Bräutigam
http://polymap.org/polymap3

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

--
Polymap GmbH
Industriestr. 85-95, 04229 Leipzig
Geschäftsführer: Falko Bräutigam
HRB 23133 (Amtsgericht Leipzig)
UST-IdNr.: gemäß § 27 a Umsatzsteuergesetz: DE253001307
Kammerzugehörigkeit: IHK zu Leipzig, IHK zu Rostock

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to