Hi Enrico, We allocated more memory to the server and don't have the OOM exception in the loading process of that file any more. We used to be able to load the same file with less memory before we added lucene index to the database. We can try to load a larger file with lucene enabled and disabled.
I can understand turning on the lucene index will require more memory. Do you have an estimate of memory footprint the Lucene index will add on top of Orientdb during regular searches and massive insert/update/delete process? Does the memory requirement increases when the database grow? Thanks, Jing On Thursday, January 8, 2015 at 2:19:15 AM UTC-8, Enrico Risa wrote: > > Hi Jing > > from what i see in the memory profile, seems nothings is related to Lucene > i will do so further inspection > Have you tried to disable the lucene index? > Do you still have the OOM exception? > > 2015-01-06 18:17 GMT+01:00 Jing Chen <[email protected] <javascript:>>: > >> Hi Enrico, >> >> I have sent you some memory profile data by email. Please check your >> gmail. >> >> Thanks, >> Jing >> >> >> -- >> >> --- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- 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.
