I have rewritten the code to use hashtable instead of list, leading to lot faster startup time on my test system ( <1s for ~40k users). I am currently testing the code ( add/remove users option ). This is for an older version of a-s (0.6.15) , will update the code against head and post.
Anything which does need the user list ( gnome-control-center user manager/ indicator-session/..) still breaks .
Personally I believe, the best solution would be to allow user to select an upper limit ( and list only cached users from login history ), and broadcast "user-limit-reached" option. The broadcast could be used by applications to display warning or change their behaviour ( such as disable user list in gdm ).
Created attachment 73763
patch
Hi halfline
I have rewritten the code to use hashtable instead of list, leading to lot faster startup time on my test system ( <1s for ~40k users). I am currently testing the code ( add/remove users option ). This is for an older version of a-s (0.6.15) , will update the code against head and post.
Anything which does need the user list ( gnome-control- center user manager/ indicator- session/ ..) still breaks .
Personally I believe, the best solution would be to allow user to select an upper limit ( and list only cached users from login history ), and broadcast "user-limit- reached" option. The broadcast could be used by applications to display warning or change their behaviour ( such as disable user list in gdm ).