Hazel/Hazelworker sloow on Yosemite!

I am running the latest version of Hazel, but ever since I upgraded to Yosemite, all file system operations are painfully slow. unarchiving, file moves and copies. Anyone else experiencing?

Mac Pro running Yosemite 10.10

Thanks!

Did you email me about this as well? If so, please try to only use one channel or the other. If you did not email, then reply back. Also, post detailed logs as well as details about the source and destinations of the file operations.

If anyone is experiencing this, can you please email support as I'm trying to collect data on this problem. Thanks.

Nope I never emailed anyone.
Right now I am experiencing it. Trying to unrar a 900 meg .mkv tv show. Been about an hour.

I will see what I can find in the Hazel LOG. Thanks for the reply.

In my case its not doing the tasks slowly, but its slow to start them, taking a lot longer than usual to pick up changes in a folder on Mavericks 10.9.5/Hazel 3.3.2.

In the photo import folder, it used to start almost as soon as the images started coming in in the couple of months I've been using it, but now its taking 5-10 minutes to start, and a similar amount on a subsequent folder the images are moved to.

I can't tell with other actions, because the photo import are the only 'real time' rules, so I just wouldn't notice.

mazeomatic: If you are interested, I want you to try a test build to help diagnose the issue. Please email support if you are up for it.

Neoncarrot: Yours seems like a totally different issue. Next time I suggest creating a separate topic. As far as your problem goes, please email in your logs and indicate the name of a file that wasn't processed along with the time it was added to the folder.

I am happy to help however, but not sure why, but after updating to 10.10.1 Hazel is working good as new on my Mac Pro.Its quick, responsive and running and picking up rules quickly.

Odd. Keep an eye on it and email support if it happens again. I've had several reports of this but no one has stepped forward with more details so I can't confirm it nor provide a fix.