Thanks MV-dev1 for your inputs regarding the issue ! @OrientDB, Yes I feel exactly the same !!
On Tuesday, 9 June 2015 16:09:08 UTC+5:30, MV-dev1 wrote: > > Hello again Kapil. > > I wrote a bug related to this last night -- see > https://github.com/orientechnologies/orientdb/issues/4327 > > GC not correcting on subsquent calls after 'OutOfMemoryError: GC overhead > limit exceeded' #4327 > > - I did mention that I was unable to DELETE as well > > > My problem got worse because once I started getting the GC limit exceeded > errors than I couldn't even close the database. Not sure if you're seeing > this? > > Also, noted there is how I added a *LIMIT 10000* to my CREATE queries so > that I didn't experience the problem as quickly. You can probably use the > same syntax for your DELETE with a SELECT. > > Finally, I read some threads which suggested increasing RAM and swap space > limits, specifically... > > - set MAXDISKCACHE=8192 (I tried 8192) > - set MAXHEAP=-Xmx512m (I tried 1024 but still had the problem) > > You can make these changes in your server.[bat/sh] and/or console.[bat/sh]. > > *600k records isn't really that big in real world scenarios, right?* > > My feedback to the Orient dev team... > > This product is one of the best things I've seen since OOP was added to >> C++ in 1989! I LOVE THE IDEAS! But, sadly, it's not ready yet for a real >> production deployment as I seem to be hitting landmine bugs at every turn. >> >> *I'm personally committed to try and help make this succeed -- I'll soon >> be digging into the code and proposing my own bug fixes instead of just >> complaining without being useful.* >> > -- --- 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.
