History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: SES-165
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Arjohn Kampman
Reporter: Arjohn Kampman
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Sesame

clearRepository() potentially slow on large databases

Created: 17/May/05 11:48 AM   Updated: 17/Jun/05 10:14 AM
Component/s: RDBMS Sail
Affects Version/s: 1.0, 1.0.1, 1.1, 1.0.2, 1.0.3, 1.0.4, 1.1-RC1, 1.1-RC2, 1.1.1, 1.1.2, 1.1.3, 1.2-RC1, 1.2-RC2
Fix Version/s: 1.2


 Description   
A call to RdfRepository.clearRepository() results in two DELETE-calls to the database:

DELETE FROM resources WHERE id <> 0
  DELETE FROM namespaces WHERE id <> 0

These calls can potentially be slow when these tables contain huge amounts of rows because DELETE-calls are usually subject to transaction management in RDBMS's. TRUNCATE-ing the tables and reinserting the 0-ID rows might be safer performance-wise.

 All   Comments   Change History      Sort Order:
There are no comments yet on this issue.