One important detail about the test screen above is that PA opens an UAC prompt asking for privileged execution before starting the test. Here’s the multi-volume compressed file opened in PA, showing the total file count and the full archive size:Īnd here’s the test results screen after I click Actions -> Test…, showing an incorrect file count and archive size (this seems to be the file size of the first volume alone): Here’s the folder I compressed, and the 28 resulting files: The test fails, showing errors in all files.
I’ve found a bug when trying to test an encrypted, 28-volume 7-zip archive of a 18.3 GB folder containing 41,751 files. Perhaps I’ve missed a way of lessening Starter’s impact, but in the meantime I’ve adjusted my set-up to running PA without it. I can understand a need to use a good chunk of CPU when Starter is actually handling PA jobs, but it shouldn’t sit and consume this amount when it really isn’t doing anything but wait for a job to start and for which it is needed. It runs, consuming this resource, irrespective of what may be happening with PA and any pbs script jobs. When I have enabled Starter as a start-up programme, to use the PA Queue facility, I see that Starter consistently uses between 10-13% of CPU, with High Power consumption indicated. I’ve also been trying to identify why my system seems rather sluggish despite some extensive tuning for speed etc. pbs jobs, I’ve been paying close attention to the system CPU resource and power consumption of PA Starter, as shown by the various resource management tools. In the course of sorting out some inconsistencies in a couple of my. I’m running W10 Pro on an HP i-7 machine with now 32gb of RAM.
0 kommentar(er)
