Short form -- you're building a transaction of changes, and you're changing a lot of records. To delete one link, you end up modifying the source and target nodes (plus the edge itself if you're using heavyweight edges). If you build a transaction with 2.9M changes, it *is* going to take a lot of memory.
- Craig - On Mon, Jun 15, 2015 at 10:59 AM, <[email protected]> wrote: > I have the same problem here. > Version: orientdb-community-2.1-rc3 > > I would like to delete 2,900,000 edges but I have the same memory errors. > Why does deleting require that much memory ? > > > Le mardi 9 juin 2015 11:47:31 UTC+2, Kapil Ranade a écrit : >> >> Version: orientdb-community-2.1-rc3 >> >> I have an edge class with about 600k records. I just want to remove all >> the records and create new edges. >> >> I cannot use "drop" or "truncate" as it says it can result in broken >> records. Use unsafe. >> >> If I try to delete these 600k records OrientDB gives OutOfMemory error >> and creates a heap dump. >> >> Any solution to this problem? 600k are NOT a lot of edges. >> > -- > > --- > 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. > -- --- 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.
