[
https://issues.apache.org/jira/browse/DIRSTUDIO-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seelmann updated DIRSTUDIO-120:
--------------------------------------
Fix Version/s: (was: 1.0.0)
The deletion of entries is implemented very ineffectively in a pessemistic way:
Before delting an entry a one-level search is performed to find out if there
are child entries. This is done recursively. Not until an entry doesn't have
any child entries the entry itself it removed. So when deleting an ou with
thousands of child entries there are thousands of searches for each child entry.
We should reimplement it more optimistic:
- use the tree delete control if supported by the server
- else try to delete the entry. If receiving an error code 66
(notAllowedOnNonLeaf) then perform a one-level search and try to delete these
entries.
This is a bigger change, lets postpone this issue and reimplement it together
with DIRSTUDIO-123.
> 100% CPU when deleting thousands of entries
> -------------------------------------------
>
> Key: DIRSTUDIO-120
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-120
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-browser
> Affects Versions: 0.8.0, 0.8.1
> Reporter: Emmanuel Lecharny
> Assignee: Stefan Seelmann
>
> When we try to delete 1000 entries, the CPU goes up to 100% for several
> minutes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
