Indesign cc19 14.0.1 is running extremely slow

Having similar issues as you.  One thing people need to know about InDesign, is it only uses 1 core of your processor!!! 1 core!  so your 8 core processor is not being used to full capacity with indesign.

I told Adobe about this about 8 years ago. They said it would require a complete rebuild of indesign to support multi-cores.  I said they better get started. 8 years later, and no change... they're just going to get more and more issues because of this defect.

Sorry, we have 16 GO and 32 GO for Ram Memomy, I was talking about Graphic card memory...

Explore this:

InDesign CC 2019 Troubleshooting How-to Guide

It might be very difficult for the original poster @ugoc35422717​ to completely be off the network, given that he's in a corporate environment. Email, file servers, security, etc. are all required in that type of set up.

I'm not sure virus scanning is the problem, either, because with today's Norton et al, the scan takes place during the computer's start-up, and then only when a new file is accessed from the server. It's not being rescanned after it's placed into INDD.

But definitely take the entire InDesign project off the server: all graphics and INDD files. The virus scan will run once and then be done once the file is on the local hard drive.

We're finding a similar slow-down on our Windows workstations, too, as well as screen "garbage" when scrolling a page, mis-displayed fonts/kerning, and other similar problems that remind us of the good ol' days of desktop publishing in the 1990s.   Stuff I haven't seen on our high-end workstations in 20 years is now a daily occurrence.

So far our testing is pointing to fonts and graphics memory. Since Adobe tweaked the former-TypeKit-now-Adobe-Fonts utility in CC:2019, the slowdown has been dramatic and I'm wondering if it is part of the problem.  We're taking the following measures and have seen some improvement:

1. All INDD files and graphics loaded from the local hard drive, never from a server.
2. Don't run via a VPN, either.
3. All fonts installed locally on the hard drive the old fashioned way: buy the fonts, download, upzip, and install into the Windows Fonts folder. No TypeKit/Adobe Fonts which seem to be a significant bottleneck.
4. Use a font manager to trim down the number of fonts that are active on the workstation. Every font you can see in the menus is taking up some of your computer's RAM. It's also adding overhead every time you redraw the screen, cut/copy/paste text, or do anything the "hits" the fonts. Here's a good overview of today's font managers: https://business.tutsplus.com/articles/best-font-manager-apps-2018--cms-31388   We use Linotype's Font Explorer for Windows, an old copy because they didn't update it for Windows 10. Has a few visual quirks, but it manages fonts very well. Trim your active fonts down to the base Windows system fonts plus the ones you need to produce your project. Here's Microsoft's list of Windows 10 fonts: https://docs.microsoft.com/en-us/typography/fonts/windows_10_font_list.  Some are required to run the system (Arial, Times New Roman, Segoe, anything with MS in its name, Calibri, Cambria, and anything that is a symbol/pi font).
5. Adjust your preferences to turn off the features that can contribute to the time "drag."
   
   
   
6. Use styles to format your text. When you manually format from the Control Panel and Properties Panel, you add overhead to your file's code. Given the intensity of the files you work on, this can add significant processing time when moving items, copy/pasting items, and saving/exporting/printing files.
7. If you're importing XML from a database into your layout, kill the XML once you have the content into the layout and the formatting styles have been applied. InDesign's XML utility is a well-know time drag.
8. Compress your INDD file as you work. About every hour or so, save your INDD file and overwrite the name or give it a new name (incremental numbering works well for this). This tactic removes any legacy history (like your undo history) and produces a lean, clean INDD file. It also is a good habit because it cleans up the file's and can prevent corruptions later on.

As I write these tactics, it feels like deja vu from the 1990s all over again .  But they've helped improve the performance of our studio's workstations on heavy-duty projects. Not as good as reverting back to CC:2018 on the same workstation, but at least it's better.

Hopefully our esteemed colleagues on this forum will have additional recommendations.

I personally don't know what Adobe did in CC:2019 that has caused this for many people. It's one of the top complaints on the forums. Just know that you're not alone!

FYI: graphics memory is something we're now looking into. Our current workstations have 4 GB on good, powerful graphics chips/cards but we're now investigating 8-16GB of graphics RAM (VRAM) on the graphics chips that is in addition to the regular computer processor RAM. Essentially, we buy "gaming" computers for our desktop publishers.

Your specs below don't list the graphics memory. Drill down in Device Manager and see what you have.

Our config :PC : win7, intel xeon 2620 8 core 2ghz, 16go RAM New PC : Intel I7 8700 3.2Ghz 32Go RAM

Hope this information helps speed up your workflow!

Let us know if any of these ideas helped. Best to you.