Deleting large amount of subgroups / users fails in CMS

Hans Kloppenborg

Posted on 08/05/2018 12:48:31

Hi,

For one of our customers we are developing an import api for users/groups, and I noticed that after importing a lot of groups and users in those groups, that the "Delete Group" option on a group with lots of subgroups (Employers) and users (Employees) in those groups no longer works. You do not get an error or something, just no reaction at all, and after waiting a long time the delete action has done nothing.

Even after deleting all the users in the subgroups using a SQL query just removing the subgroups still fails. Seeing that it is only 1060 subgroups with each 1 subsubgroup themselves, it should be managable I would think.

Could you check if this can be fixed? This was tested with DW core 9.4.10.

Greets Hans

Replies

Dmitriy Benyuk

Posted on 11/06/2018 10:28:34

Hi Hans,
I was able to reproduce your issue by inserting the 1060 subgroups that have one child subgroup. After clicking "Delete" on the top group the deletion process is starting but the performance is very bad so it takes around 2-3 minutues to complete, but actually the groups were deleted. So this is just a performance issue.
TFS# 51354 created.
Regards, Dmitrij

Martin Vang

Posted on 14/06/2018 14:15:20

Hi Hans,

This amount of data is not something that we currently support. I've rejected TFS# 51354 - it is not something that we have ever supported. Im not comfortable with a rewrite of our Group.Delete method for a hotfix (its going to become WAY too hot).

If you have a case for using this in the real world, I would like you to create a feature request for supporting more users.

For now, I would suggest you delete the groups with a sql-command.

Martin

Hans Kloppenborg

Posted on 14/06/2018 16:33:02

Hi Martin,

It was a one time action, so it is not a real problem to use SQL queries in this case, but I am curious what the official amounts of users and groups are that DW supports without issues.

For this website we got 100K + users distributed in an A-Z grouptree with company subgroups, and that works OK in back and frontend in most cases, but our customer is complaining that configuring smartsearches has become impossible. Is this number of users to much for DW?

Greets Hans

Nicolai Pedersen

Posted on 14/06/2018 16:47:44

There are none - it is the rule of 'common sense' and the amount of hardware. It works, but it is slow. Is the most common use case that I create a structure with 2000+ subgroups?? We do not see that often...

Martin Vang

Posted on 15/06/2018 09:32:02

Things should work for up to 10000 User Groups, 1000000 Users and 300 concurrent frontend users.

These numbers heavily depend upon hardware as Nicolai pointed out - fx. adding Load Balancing to the mix, increases the number of concurrent users a very high number (a guess for a typical machine that handles the network load would be... maybe 2000000 concurrent users). :)

If you create 1 group with 9999 subgroups and place all users in each group, things will probably begin to fall aparat in a few places - we havn't had anyone who needed this, yet (and we probably wont ever have anyone who actually need this).

Hope this answers your question?

You must be logged in to post in the forum

Developer forum

Deleting large amount of subgroups / users fails in CMS

Replies