Unimpressive CPU Usage, max 10%-12%

[TFarrell9]

5 minutes ago, rgrin said:

Some new info.

 

I opened a different file and started regenning toolpaths.  Memory usage did not climb at all.

Reopened the problem file and started regenning. Memory usage started to climb....

 

Corrupted file or something?

Have you tried Repair File yet? 

[rgrin]

@TFarrell9

I have previously.  Can't recall the results...

I'll try it again.

 

Edit: Tried it and got "Database did not need to be changed" pop up.  Still exhibiting the same memory climb issue

[Greg Williams]

16 hours ago, #Rekd™ said:

How does the file size compare?

Like most things, it depends on how you use it. When you let NX build the IPW (Stock Models) internally in the background, the file size can grow significantly. With IPW building turned off, the file size is comparable to Mastercam. However, with IPW building on, a 100MB file can quickly expand to 1GB, especially if the part is organic and reasonably complex.

CAM is inherently complex across all systems. While computers continue to become more powerful over time, parts are also becoming more intricate, and 5-axis toolpaths now carry more data than ever before. As a result, the load on systems is steadily increasing. Multithreading, in particular, is a highly complex arrangement that adds to the challenge of CAM and simulation.

 

Just my .02 worth

[crazy^millman]

Part we did in X9 that was over 3500 operation and 10 Mastercam files each well over 1gb wouldn't even be considered if I was asked to do it in 2023, 2024 or 2025. Just to give you my experiences with the software of late. Most have been documented and confirmed and the answer is just go to 2025. Again that decision is out of my control for a majority of our customers no matter how many time we talk about moving to a different version. Got my butt handed to me lately and trying to explain to someone why a 30 second process take over 6 minutes that should only;y take 30 seconds is a real hard one when they want it yesterday. Parts done in 2021 where I had 5 or 6 different part models and fixtures and everything is not even an option anymore. The customer is getting 20 or 30 different Mastercam files now and up to them to sort out what to do if there is a rev change. Have 16 parts all pretty similar when I did this in 2021 I had 6 different parts. The Trunnion, and most of the fixture components was shared. Just change a few items and the part models between the parts. Worked great in 2021 see which wall you paint 3 weeks ago is drying faster in 2024. 3 day job doing a mirror of part in 2021 11 days in 2024. Maybe 2 restarts a day in 2021 20 a day in 2024. Oh yeah you need to pay more to use the software that is loosing you money.

[cncappsjames]

On 9/6/2024 at 9:08 AM, Cavi Mike said:

I love how you guys constantly blame the user for not only the faults of MC but also the faults of yourselves. It's not his fault MC hasn't done a single thing about its terrible resource utilization. Just because processors were all single-core back in the day doesn't mean MC can't spend some time adapting it for multi-core processors. Multi-core processors have been the norm for like 20 years now. Yet another user lost to Siemens.

Go back and read ALL of the replies.

You're jumping in mid-conversation, and honestly with nothing constructive to add, so there's that. 

NX offers things the majority of CAM focused software will most likely never be able to offer. NOBODY is migrating to NX expressly for the toolpaths it creates. They migrate mostly for the engineering and simulation components of the package, the CAM just ends up being a +1. 

I've got quite a few customers on the NX train. I've seen the workflow, I've seen the capabilities, I've seen the power, and I've seen some of the issues. They just don't get talked about nearly as much as they do in Mastercam... partly because they have a fraction of the user base, however much like HyperShill, if you talk publicly about the software's failings, you may find yourself "in the queue" permanently for support.

I'm just saying...