[Neo4j] neo4j REST server configuration
jacob at voltvoodoo.com
Tue Aug 10 10:32:22 CEST 2010
Apparently the email list deletes attachments it does not recognize, I'll
send it directly to your email.
As far as the test failures go, I don't know what causes that. I ran and
passed all tests with the patch, but the trunk version should do that too.
It might be something platform specific.. what platform are you running on?
On Tue, Aug 10, 2010 at 10:06 AM, Brock Rousseau <brockr at gmail.com> wrote:
> Hey Jacob,
> The patch sounds perfect, but I didn't see an attachement. Did i miss it
> The standalone project built fine for me, but we're getting these test
> failures for mvn install on the rest component:
> Failed tests:
> Tests in error:
> Should we be running the install by ignoring tests or should those be
> On Tue, Aug 10, 2010 at 12:33 AM, Jacob Hansson <jacob at voltvoodoo.com
> > Brock,
> > I've written a patch that allows setting the max threads via the neo4j
> > configuration file. Applying it fixes the problem you mention, but leads
> > some kind of resource starvation higher up. This is not as critical, at
> > concurrent requests it will make the server alternate between 12ms read
> > response times (which should be the norm) and 300ms. It's still bad, so
> > before this patch is applied I'd like to dig into where that comes from.
> > If you want, though, you can apply the patch yourself. To do that, you
> > would
> > download the REST component and the REST standalone project, avaliable
> > here:
> > svn co https://svn.neo4j.org/laboratory/components/rest/
> > svn co https://svn.neo4j.org/assemblies/rest-standalone/trunk/
> > Apply the patch (attached to this email) to the REST component.
> > Run "mvn install" on the REST component, and then "mvn package" on the
> > standalone project. This will give you a patched version with a default
> > thread count of 128 (compared to 5 before).
> > To increase it more, go to the "neo4j-rest-db"-folder in the deployed
> > system, open (or create) the file neo4j.properties, and use the following
> > two settings to modify the thread count:
> > rest_min_grizzly_threads=16
> > rest_max_grizzly_threads=48
> > I can't give you a "perfect" number, but it makes a big difference in
> > response times, in both directions, to change these settings.
> > /Jacob
> > On Mon, Aug 9, 2010 at 8:51 PM, Brock Rousseau <brockr at gmail.com> wrote:
> > > Hey Jacob,
> > >
> > > Thanks for the quick response!
> > >
> > > We saw your post on the grizzly mailing list about the transaction
> > > fix. Is that something we'd be able to implement on our end today?
> > > had
> > > to throttle back the traffic significantly and are eager to see it in
> > > action
> > > at full volume.
> > >
> > > -Brock
> > > _______________________________________________
> > > Neo4j mailing list
> > > User at lists.neo4j.org
> > > https://lists.neo4j.org/mailman/listinfo/user
> > >
> > --
> > Jacob Hansson
> > Phone: +46 (0) 763503395
> > Twitter: @jakewins
> > _______________________________________________
> > Neo4j mailing list
> > User at lists.neo4j.org
> > https://lists.neo4j.org/mailman/listinfo/user
> Neo4j mailing list
> User at lists.neo4j.org
Phone: +46 (0) 763503395
More information about the User