How do you force an APP to use more CPU resources?

[thecrownguy]

I have searched and searched for an answer for this and I feel stupid asking it. I am not new to Mac and I just cannot figure this out. I have about 400 .zips that need to be unzipped in a single folder. I can highlight them all and it starts unzipping just fine. However... at 2.5% CPU putting along like a maid on hourly pay. All the time an enormous amount of headroom is just wasted. By my calculations, it will take 5 days.

How do I make archiver hammer the CPUs and get this task done? I have assigned the priority in terminal and that doesn't help either.

I have the Horsepower with Dual Hex Cores. All the specs are in my sig. There has to be a way to be able to tell a mac... "Ok... this is all you have to do for an hour... EAT!!!" That sucker ought to ramp all the cores up and go.

Thanks for any help.

 

[Darth.Titan]

You’ll find unzipping much faster via command line.

• open Terminal
• type cd<space>
• drag your directory of .zip files to the terminal window (this will auto populate the path to your folder) and press enter
• then type unzip *.zip

in my experience it’s much faster than the GUI. If my instructions suck, google OS X terminal unzip and read a bit. Hope that helps.

 

[thecrownguy]

You’ll find unzipping much faster via command line.

• open Terminal
• type cd<space>
• drag your directory of .zip files to the terminal window (this will auto populate the path to your folder) and press enter
• then type unzip *.zip

in my experience it’s much faster than the GUI. If my instructions suck, google OS X terminal unzip and read a bit. Hope that helps.

Why didn't I think of that? I do a lot of things command line, and that did not dawn on me. One question, is there a command that can be added to delete the archive after unzipping? I will google it as well.

Thank you Thank you!
[automerge]1585605503[/automerge]
UUUUGh! This is what I get
zsh: permission denied:
[automerge]1585605963[/automerge]
Now I am getting this

 

[ApfelKuchen]

Just keep in mind that for these kinds of actions, pushing the CPU may not make a difference. For something like unzipping, disk i/o and disk read/write tend to be slower than the CPU. Further, it may not matter at all that you have all those cores. If the unzip code is written as a single-core process, single-core is what you'll get.

 

[thecrownguy]

Just keep in mind that for these kinds of actions, pushing the CPU may not make a difference. For something like unzipping, disk i/o and disk read/write tend to be slower than the CPU. Further, it may not matter at all that you have all those cores. If the unzip code is written as a single-core process, single-core is what you'll get.

I just realized these files are on a spindle drive. DOH!!!! The read-write is about on point. I am stupid.

 

[chown33]

I recommend that whatever you try next, do it first using only 10 zip files. If that means moving 10 zip files into an adjacent folder, then do that.

After you've figured out the exact command-line that works on the 10 zip files, only then should you go back and do it on the remaining 390.

I would even go so far as to say do a stage-2 test using only 50 zip files, then double the number of files each time you repeat it.

The overall goal is to experiment on small numbers, test the results of the small experiment on medium numbers, and never try too much at once without having it already proved out in earlier and smaller trials.

 

[thecrownguy]

I recommend that whatever you try next, do it first using only 10 zip files. If that means moving 10 zip files into an adjacent folder, then do that.

After you've figured out the exact command-line that works on the 10 zip files, only then should you go back and do it on the remaining 390.

I would even go so far as to say do a stage-2 test using only 50 zip files, then double the number of files each time you repeat it.

The overall goal is to experiment on small numbers, test the results of the small experiment on medium numbers, and never try too much at once without having it already proved out in earlier and smaller trials.

You are 100% correct. I just have it plugging away in the background.