The correct fix is to select all the geometry inside the cable component, and set it to Layer0 (or untagged in 2020). Then set the Cable component to the cable layer.
After a couple of hours, the purge finally returned. I then did the cleanup3.
Wow! What a difference. The performance for my needs is now adequate. Thanks to Box and DaveR for the tip to do this!
I triple clicked on the wires as Box indicated and change their layer from “blank” to layer0 (I’m on SU 2018). Then I assigned the component to cable layer. Now’s all good!
I post questions to many forums. The replies on this forum are the fastest and best by far. DaveR has been especially helpful over a long period of time, typically with a timely reply just minutes after I posted the question, even at strange hours.
Wow! On my computer it took 1 minute and 47 seconds. to complete the purge. It would be nice if Sketchup showed a progress bar instead of freezing things indefinitely.
My processor isIntel(R) Core™ i7-7820X CPU @ 3.60GHz, 3600 Mhz, 8 Core(s), 16 Logical Processor(s)
I have 8 GB memory, and lots of unused motherboard SSD storage (hundreds of Gigabytes.).
This was about the best available around 5 years ago. The performance I was seeing made me wonder if it was time to buy a new system. But, after the purge, performance is reasonable for everything I’m doing.
Sketchup (and all cad) is a single thread operation, it can only take place on one core. So it’s possible for Sketchup to be locking up it’s single core with work while system diagnostic says there is still available resource.
Here are two versions of purge in real time on your file.
The longest part is in the middle when I revert back to do the second purge.
This is on a slower PC
I suspect there is some tweaking that needs to be done to your system if it is taking so long.
That didn’t make enough difference to get the kind of performance your gif shows (still running after restarting). Could the installed extensions make a difference?
I did add one that monitors changes to the active layer and issues a warning when it’s changed. Maybe something gets triggered and has to time-out during execution of the purge command? Just a WAG.
Not a pressing issue for me, since the purged file has good performance. Besides, I wouldn’t know what/how to “tweak” or investigate further.