I'm loading the dataset via a custom - sql.
Hemant, we need more info to help.
As you use a Custom SQL, problems can have many causes.
Are you working in live mode?
Yes, I'm working in Live mode. When I work on extract, the filter is much faster. The query executes in less than a second, so I don't understand why does it take so long to filter.
This might help you. Please ignore if its not.
If you have the second filter to have many unique members, say like 1500 unique members, then there are possibility that the performance could be slow. If that's the case, try making it less unique, like Categorise them on Data level if possible. Just sharing this with my experience on similar filter slow issue.
I just have 12-15 unique members.
Then my below explanation to be ignored Pls check the custom SQL, if you can, pls share us the SQL.
Experts here would help you for sure.
If one filter is faster and other not, maybe one of them have an index created on database.
If you can check indexes and create if not exists.
I'd recommend use extracts.