Deletion performance can be very bad

EVGENIAST / cumulusrdf

Automatically exported from code.google.com/p/cumulusrdf

0 stars 0 forks source link

Deletion performance can be very bad #34

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

Deleting from the store will trigger one test for deletion from a secondary 
index for every triple. Using a hashtable or sorted tree as buffer would 
increase performance here.

Original issue reported on code.google.com by Isib...@gmail.com on 11 Feb 2014 at 11:02

GoogleCodeExporter commented 8 years ago

Original comment by Isib...@gmail.com on 11 Feb 2014 at 1:14

Changed state: Fixed

GoogleCodeExporter commented 8 years ago

Using a Java hashset now to prevent duplicates.

Original comment by Isib...@gmail.com on 11 Feb 2014 at 1:15