Received from Luca Garulli on Tue, Aug 04, 2015 at 08:00:56PM EDT:
>
> On 4 August 2015 at 20:05, Lev Givon <[email protected]> wrote:
>
> > I'm running a Gremlin script (via gremlin.sh) against an OrientDB database
> > accessed directly as a plocal storage that creates new edges within a
> > sideEffect
> > called for a traversal of an existing graph. To speed up processing, the
> > pipeline increments a counter within the sideEffect and calls g.commit()
> > for
> > every N new edges. When I tried raising N to 2000, I encountered
> >
> > "Max cache limit is reached (3000 vs. 3001), sync flush is performed."
> >
> > warnings. As per [1], I tried explicitly setting the disk cache size by
> > including
> > the lines
> >
> > import com.orientechnologies.orient.core.config.OGlobalConfiguration
> > OGlobalConfiguration.DISK_CACHE_SIZE.setValue(8192);
> >
> > in my script before creating the OrientGraph instance, but that didn't seem
> > to have any effect. Any suggestions as to how to eliminate the above
> > warnings? I'm using OrientDB 2.0.13 on Ubuntu 14.04.2.
>
> Hi Lev,
> Where did you set the disk cache? It must be executed before to use
> OrientDB. Please try setting it at the beginning of your main.
>
> Best Regards,
> Luca Garulli
I set it immediately before the line
g = OrientGraph('plocal:/path_to_database')
in the script.
--
Lev Givon
Bionet Group | Neurokernel Project
http://www.columbia.edu/~lev/
http://lebedov.github.io/
http://neurokernel.github.io/
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
