Thank you for replying.
Not really a real-world use-case. Just benchmarking to see where things
break. At the moment I am only storing id (the mysql id - we're gonna go
hybrid for a while) and name for each product. I will mostly be working
with gettings sets of IDs of products via complicated paths, then look up
the rest of the product details elsewhere. I have not tried to store all
data in neo4j as yet, I wanted to check the lucene index performance first
via the neo4jPHP / REST API. BTW are you aware of paging in lucene? I can't
seem to get a good doc reference anywhere.
The stack trace is mostly OOMs at random places, not the same each time. So
I guess those wouldn't interest you. Only one actually brought the server
down. After this the server ran but no connections could be made to it. So
I paste this one. If you need more, I'll be happy to oblige.
Mar 28, 2012 5:57:41 PM org.mortbay.log.Slf4jLog warn
SEVERE: Problem scavenging sessions
java.lang.OutOfMemoryError: Java heap space
at java.util.HashMap.newValueIterator(HashMap.java:860)
at java.util.HashMap$Values.iterator(HashMap.java:927)
at
org.mortbay.jetty.servlet.HashSessionManager.scavenge(HashSessionManager.ja va:265)
at
org.mortbay.jetty.servlet.HashSessionManager.access$000(HashSessionManager. java:44)
at
org.mortbay.jetty.servlet.HashSessionManager$2.run(HashSessionManager.java: 219)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)
Mar 28, 2012 5:57:41 PM com.sun.jersey.spi.container.ContainerResponse
mapMappableContainerException
SEVERE: The exception contained within MappableContainerException could not
be mapped to a response, re-throwing to the HTTP container
java.lang.OutOfMemoryError: Java heap space
Mar 28, 2012 5:57:41 PM org.mortbay.log.Slf4jLog warn
SEVERE: /db/data/cypher
java.lang.OutOfMemoryError: Java heap space
Thanks again for your input!
--GM
On Wednesday, March 28, 2012 7:44:07 PM UTC+3, Michael Hunger wrote:
> I think it is just the amount of data held in RAM to generate the JSON
> response that causes your OOM (this is not streaming right now).
> Is it a realistic scenario to return 500k items over the wire? Each
> product is a note which will be rendered in the quite verbose
> Neo4j-REST-API-JSON format.
> Can you try to return just a property of the product or ID(product) or at
> least pre-aggregate the data to a sensible output?
> There is an option for a more compact output format: Accept:
> application/json;compact=true but I just saw that the cypher result
> formatter doesn't respect that (which is a bug).
> Can you share the stack-trace where the OOM occurs?
> Thanks
> Michael
