I note that leaving Yummy to run eventually completes the process and processor usage drops.... I guess comparing a lot of files is pretty processor intensive?

I got Yummy as it seemed like the ideal candidate to schedule backups of remote dynamic websites, in that the site I want to back up have files added to them on an hourly basis.

Yummy seemed to fit the bill as it was capable of running a scheduled one-way sync - i.e. from server to my local back-up machine.

However, more often than not, Yummy starts to chew my processor, often gobbling up more than 70% of the CPU cycles over a prolonged period.

Does anyone know what might be causing this?

I am only connecting to about 7 sites, and even if I close connections to those not currently backing up I still get a massive chunk of processor used up.

The schedules I run should all be out of sync with one another, so no 2 are running at the same time and each runs only about once every 7-10 days.

Currently I have 2 connections open, "Analyzing Directories for Update Mac..." and still loosing over 70% of my processors to Yummy.

Admittedly, due to the nature of these sites there are a lot of files/folders... is it possible Yummy gets confused when a remote site has over a certain number of files/directories? One site has 600 or so at root level and the other is now up to 1100!! (I know that's quite a lot - but a shames Yummy can't handle it?)

I'm running an old Dual G4 500MHz, with over 1GB ram and an 8Mb connection to the Internet. I would have thought that was OK??

An help appreciated!