the `isIncluded` here would be called for each and every change event received from the binary log. The table include list for a task can not be updated without re-creating the task, hence it would make sense to cache the results of this table filtering in-memory rather than doing this seemingly repititive table filter computation on every change event.

We recently encountered a case where CPU usage was extremely high and this was found to be the culprit. The regex specified for the task was very suboptimal, which lead to huge time being spent in the filtering part.