I recently created some visual filters with the idea of doing a source analysis of Luke; ie I had generated lists of verse references for M, Q, L and then created a visual filter for each searching for * in that specific search range ESV.
Obviously this would slow things down; however I was surprised upon opening Logos 4 today and opening ESV that the CPU started churning at 100% despite these visual filters being turned off. There was nothing in the log to indicate what was happening, the only way to stop it was to delete the visual filters before re-opening the ESV (after which it is back to normal).
Obviously creating visual filters for * even for a limited verse range is not a great idea performance wise but I don't see why it would give a performance hit if the visual filter isn't turned on...