Stan,
Been using this filter in this manner
411,501,402,321,600,,,,,, and it works perfectly. However if I use it in this manner ,,,,,411,501,402,321,600 (the segments examples only) it is virtually unusable because of slowness. My bulk segments CSV file is quite large ie 2000 lines so there is a lot of work to do. But why OK one way and not the other?
eg in the first mode took about 4 hours to process 1.8m tickets, in the second mode it takes about 4 hours to process less 100,000 tickets.
In respect of memory allocation I have tried the default, 256, 512, and 1024 allocations and it makes not a scrap of difference.
Thus is the filter designed to only work with the segments in the first position settings, or is it universal as to how the segments are placed in the columns?