Help with a very low start only on networks, when using winapp2.ini

Hello everyone! 5h0qs.gif

I need help with the following winapp2.ini, attached. It takes minutes to make "Run Cleaner" button available when used on a network. While CCleaner is busy, we can see some network link usage on the task manager.

How correct this?

jg2t4.gif

winapp2.zip

Which version of CCleaner are you using?

Also is it paid or free?

nodles, thank you for the fast reply!

EXE version is 3.27.0.1900. Free version, home network of 2 XP SP3 computers.

How do you use free version to clean over network?

You could check Trim which can be found in the first post of Winapp2.ini

No, I'm not selecting any item to clean over network, this is not wanted.

I'm saying that the "Run Cleaner" button stays unavailable for a long time. When this happens, is noticeable some network link utilization.

It is run from a network share that doesn't have write access and has a lot of subfolders: movies, pictures, etc.

please read the spoiler section on the above linked thread (wherein it say a big file will take a long time to load). On top of that you're trying to use it over a network. Are both server and client wired onto the network or is (at least) one running wirelessly.

In addition if the spoiler section does not help, and if your ini is based on the community edition please continue the discussion in that thread, if possible.

Finally just because an app is portable (a la CCleaner) does not mean it'll run well over network (a la sysinternals apps which can be run "live" from the MS servers.

Thanks for all the replies 5h0qs.gif

Even using trim.bat with all described procedures the startup it is really slow (takes minutes bYM5b.gif) and not by using CPU time but about 10% of the network link. It is a wired network, fast ethernet 100mb full duplex. For instance, file transfers happens at full speed. When the same CCleaner set (exe + ini's) is run from a USB Flash Drive, execution is much faster.

Seems that the current state of development has issues when run from a network share (maybe because it is in read-only mode? I'm not sure).

I would never consider running CCleaner from a network.

If CCleaner is read-only then I do not see how Trim.Bat would be able to create a reduced Winapp2.ini in the same folder.

Perhaps it was prevented from achieving its intention and WinApp2.ini is still the original size.

10% of 100 Mb is about 10 Mb per sec. I do not know but assume b=Byte and not bit.

A 300 KByte WinApp2.ini can be transferred at 10 MByte/Sec in 30 mSec as a continuous stream.

BUT

A typical full size WinApp2.ini is 8597 lines long

It is quite conceivable that CCleaner was NOT designed to stream the file and then process it,

it might actually read one line at a time and process that line and then access the next line,

I do not know what latency might be involved in your network providing the next line,

so I will guess at 38 mSec (typical internet Ping delay between Lancashire and BBC.COM)

that comes out at 38 * 8597 = 326686 mSec = 326.686 Seconds

i.e. over 3 minutes.

Trim.bat surely has done his job, it was run on the server.

What was the original size, and what the "Trimmed" size ?

I'll not have access to the involved systems until next week, so I can't tell about exact .ini file sizes. But trim.bat has done his job since it was run on the file server, I have full permissions, extracted the latest portable build, selected desired options at CCleaner.exe on the server... And then, was noticed the huge delay to start when run from this read-only share, while it keeps using network link (for what? unnecessary).

I've found as conclusive that the root cause of the problem was the way CCleaner works when run from a network share, since the same set of exe and ini's was run with the expected speed when located at a usb flash drive, even before and after running trim.bat.