Hi, Could you send us hprof, it is really interesting. What is your db size ? What settings do you use ?
Do you have 3 billions instances of disk cache ??? What is your pattern of db usage ? It seems like you create storage for each operation, what is your typical test which throws OOM. Could we see it ? On Fri, Nov 28, 2014 at 5:10 PM, Xander Uiterlinden < [email protected]> wrote: > Hi, > > We've been using OrientDB2.0 M3 in testing a couple of days now. When > using M2 it was running out of memory every other day but since we we're > not using connection pooling at that time I thought that could be the > reason. Now we've enabled connection pooling and upgraded to M3 it still > happens. > > See below a screenshot of the objects after reading the hprof file into > YourKit. Maybe it rings a bell ? I could send the hprof if you're > interested. > > > <https://lh6.googleusercontent.com/-0hcMx4TkOWo/VHiPi1diiJI/AAAAAAAAA2g/PQvEAyJhbak/s1600/Schermafbeelding%2B2014-11-28%2Bom%2B16.02.39.png> > Thanks, > > Xander > > -- > > --- > 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. > -- Best regards, Andrey Lomakin. -- --- 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.
