So for the last several months, Bridge CC has had terrible performance, with preview/thumbnail generation taking much longer than it ever did in the past, using 100% of CPU resources while doing so, constantly locking up and even locking up overall system function, even with Bridge.exe set to low priority.

This happens on both systems I use (an i7-4790/24GB/GTX 980 desktop, and a i7-4712/16GB/Quadro K1100M laptop). Both are using SSD for storage.

I have:

Cleared bridge cache.

Added dedicated bridge cache SSD to desktop system (no other use)

Updated all CC software to newest versions as available

Done clean installations of CC software, graphics drivers on both systems

Tried "prefer embedded" thumbnails (has no appreciable effect)

Turned off exporting cache to folders

Turned off high-quality previews

Turned off 100% previews

Turned off preview panel

Turned off favorites panel

Read numerous support threads and tried long-shot fixes like removing windows favorites folders and random registry fixes.

I am at my absolute wit's end with this piece of software. Not sure what has changed, but after over a decade-plus of use, I am ready to cancel my CC subscription and take my business elsewhere.

For instance, I just did a fresh Cache purge after the latest CC updates today, and opened a folder of 1200 D850 NEF files. The system sat at 100% CPU (99.8% of it Bridge) with Bridge consuming 14GB RAM, for about 20 minutes before the folder was able to browse or be used. Or the entire PC for that matter, as even with Bridge set to low priority, mouse movement and click recognition was very hit and miss.

Every time I launch Bridge (and, it seems, other Adobe CC apps) I get a smallish white dialog box with no information other than a circular blue progress indicator. My guess is that it is checking that it is a registered app.
I was under the impression that it only checked once every couple of months, but this happens with every launch.
In addition my Internet was down the other day and I was unable to launch Adobe apps as a result. This means that I must always be connected to the web to use my Adobe CC apps. This is surely not correct?

I run several QHD (2560 x 1440 px) monitors, two 25 inch and one Cintiq 27 pen display. There's no way to display Bridge well with the options given in Preferences. The largest scale in 100% is way too small, automatic seems not to do anything and at 200 and largest font everyhing is gigantic.

Usability is seriously hampered, as tools like batch renaming are extremely small. Generally, the GUI displays a questionable hierarchy of font sizes. Address bar font larger than Main menu, Search field text very small, Thumbnail Tooltipps on Hover even ridiculously small (maybe 6 px). This all looks very unrefined. I'm also surprised to see stuttering when dragging the borders of the sidebars. This should not happen on a modern machine.

I run several QHD (2560 x 1440 px) monitors, two 25 inch and one Cintiq 27 pen display. There's no way to display Bridge well with the options given in Preferences. The largest scale in 100% is way too small, automatic seems not to do anything and at 200 and largest font everyhing is gigantic.

Usability is seriously hampered, as tools like batch renaming are extremely small. Generally, the GUI displays a questionable hierarchy of font sizes. Address bar font larger than Main menu, Search field text very small, Thumnail Tooltipps on Hover even ridiculously small (maybe 6 px). This all looks very unrefined. I'm also surprised to see stuttering when dragging the borders of the sidebars. This should not happen on a modern machine.

Bridge 2021 11.0.0.83
Hi, first of all, in general I love Bridge, providing all I need for Photo Management!
I observed the following performance issues when updating my photos stored on a NAS (SMB access).
Batch or Mass updates of Filenames or Metadata (Keywords) is extremely slow (even for SMB access).
I am using Bridge on my Apple Silicon M1 MacBook Pro.
When Batch renaming 150 files it took >15min before I 'killed' Bridge manually. It was using 1 core at 100% and took ages to complete the update. It might be related to updating the Cache DB, because the filenames where already updated completely.