Large Log Files - Rules Going Into Subfolders

(1) Within a week, my Hazel log file reaches 10-15 GB. Is this normal with my setup? I have 16 rules focused on...

- Add/Remove tags
- Rename folders and files based on filenames or contents
- Delete/Move folders and files based on filenames or contents

(2) Can a rule for the action *Go Into Subfolders* prevent Hazel checking every subfolder and file when I make one change within? I have 964 subfolders. Each folder has 1-3 files. I know it will run on all folders and files if I restart my computer but what about after it's done it's initial pass?

> https://www.noodlesoft.com/manual/hazel ... ubfolders/
>
> If the monitored folder has a very deep hierarchy of subfolders, processing them repeatedly can take a long time and can negatively affect Hazel’s performance. For best results, use this approach on relatively shallow folder hierarchies, or use the “Subfolder depth” attribute to limit how deep the rules go.

(3) Will Hazel jump to a modified file and make changes then go back to its lengthy subfolder scan? I noticed while Hazel is scanning my subfolders, if I make a change to a file, it focuses on that file then seems to go back to its original subfolder scan. Is this correct?

1. You need to look at the log file. Given #2, it seems you are going into a lot of folders, possibly unnecssarily.

2. Do you really need to keep tabs on all those folders all the time? Can you provide more details on what you are doing?

3. It's a bit more complicated than that and trying to figure out how it works exactly is probably not the best approach here.