We have about 180+ users, and around 8-20k jobs.
Toggling any of the user filters can take anywhere from 1-5 minutes, even when the filtered job list is very small (~20 jobs displayed).
Its bordering on unusable, and the machines are very high performance.
cheers,
laszlo
We may have to rethink how the quick filters work. Currently, the quick filter system is just a layer over the regular filter system. Every time you uncheck a user in the quick filter panel, it adds a “NOT THIS USER” filter. So if you uncheck 120 users, that’s 120 “NOT THIS USER” filters that each job has to be checked against. The common use case for the quick filters is probably that you want to only see jobs for one or two users, plugins, etc, so it would probably be more efficient to invert how these filters work. I could see us adding the option to invert the filtering. That way, if you only have 1 or two users checked, there would only be one or two “THIS USER” filters, which should speed things up.
Thoughts?
Cheers,
Ryan
If you think it would speed it up, im all for it! It seems like its the toggling thats slow, and once the state is set, it seems speedy.
Also, turning OFF all the users is an order of magnitude slower than turning them all on, which takes only a couple of seconds, which tells me its not a gui speed issue.
That’s because turning off all users adds 180 filters to check against for each job. It’s faster when you turn them all on because under the hood, all the filters are simply being removed.
So you’re right, it’s not a UI issue, it’s how the filters are created.
I’ve logged this as an issue targeting Deadline 7.
Cheers,
Ryan