Skip to main content
July 21, 2020
Question

Code processing on single core?

  • July 21, 2020
  • 3 replies
  • 783 views

Why does Microsoft's Performance Monitor visually report that the reason AI is taking so long to open and re-save a 1.7 GB file, and crashing randomly, seemingly is because it's using only one of the many CPU cores?

No parallel programming yet to take advantage of at least 2 or maybe even more of the available cores?? 

All system resources are well under 25% max. (Overall CPU is at 1% - 3%, memory below 10%, SSD 0%; yet 1 core is pegged at 100% and even 125% [overclocked] when AI is saving and sometimes crashing) load, and AI is having a very difficult time. CS6

Let's just all go back to chiseling on stone tablets.

This topic has been closed for replies.

3 replies

lindav13427399
Participating Frequently
July 21, 2020

I am having endless problems with AI taking forever to save large files and very often crashing.  Making my life a living hell. All started after the last update.

 

Monika Gause
Community Expert
Community Expert
July 21, 2020

"I am having endless problems with AI taking forever to save large files and very often crashing."

 

Please don't hijack threads. Yours is a different issue. Please create a new thread, tell us your system, version and hardware and the nature of your files. And then describe your issue.

Monika Gause
Community Expert
Community Expert
July 21, 2020

CS6 is the equivalent of a stone tablet.

While all what Mylenium wrote applies, Illustrator has improved speed over the last versions.

July 25, 2020

What version over what versions?

Mylenium
Legend
July 21, 2020

Adobe programs use standard system APIs and file systems. Not sure what you expect to happen here. 1.7 GB is simply a huge file and the file I/O behavior wouldn't change even if AI itself was a much better optimized program. This stuff would have to change much more fundamentally in Windows itself and that's beyond Adobe's sphere of influence. The only thing they could fix are poitential crashes which no doubt relate to generating file previews and messing with internal data structures, but that's about it.

 

Mylenium

July 21, 2020

If a file is "too big" for AI to handle reasonably (over 80 layers), why not throw a warning to the user, or allow layers to be moved between AI documents effortlessly (unless they drag and drop now...) to breakup/transfer or downsize (layers) per file if necessary (instead of copying/pasting the entire layer, i.e., many clicks vs. a few).