Possible bug in Connect X7 on local drives.
One of the first things I noticed with connect is the huge performance improvements, looks as though they are relying on Microsoft indexing more heavily compared to X6, this is good.
However, I am seeing a huge lag in new files being displayed in connect; this is because it is not displaying files unless they are indexed.
To duplicate, simply create a new .cdr or .cpt file in a folder and see if it appears in connect right after saving. Then wait awhile and you will see it appear after windows updates the indexes.
Also, I noticed a sizable increase in CPU utilization compared to X6 that is not released when closing connect, requiring a restart of the search process.
Can someone verify this?
You are correct about Windows indexing...CONNECT won't show results unit the location is indexed.
Can you give me more details on the CPU issue? Which locations were you searching? How many searches had you preformed? What kind of content (jpg, png...) were you searching for? Any info you can share with us would help us track this one down.
Hmm... This could be a problem with solid-state drives because it's recommended to turn off indexing for SSDs so the drives last longer. Well, it's good to know anyway.
I wonder if this is why I couldn't see the bitmap fills that I downloaded in my Connect tray.
PixelDust said:it's recommended to turn off indexing for SSDs
I've never heard anybody recommend that. Are you thinking of turning off defragmentation? Or is this just a hangover from the SSDs of the previous century?
Logically, turning off indexing will probably if any thing increase the wear on the SSD. When you index the drive, windows indexes the drive once and builds a database of its filenames and keywords so that it can find files many times without the need to search the entire drive again. It then, presumably, keeps track of new files as they are added and modified and only needs to fully reindex occasionally. But if the drive is not indexed, then windows must access the actual drive every time you perform a keyword search, rather than just looking it up in the index database.
It is also slightly questionable to buy an SSD -- supposedly to improve speed -- and then turn off beneficial services to make it less efficient.
Thanks for responding.
What I am seeing is:
Fresh boot: index fully indexed, resources at 0-1%
Open connect: indexer begins indexing 25-30%, this can take a while.
The behavior appears to be connect is putting the indexer into a “notification-enabled” mode when opening causing the higher resources.
To demonstrate this, open the index option dialog, if it is indexing, wait until it is completed, then open connect, and note indexing starts, this happens every time connect is opened.
I don’t believe implementing this at the directory level was the best decision, for a file to be saved to a directory and then requiring an index prior to selecting said directory will create many problems in one’s workflow.
In other words, index should be used for searches only, if I select a folder, a file scan should be used, even if it provides a slower response.
For example, I copy a file to a folder in windows explorer, and because I am working on the computer the indexer is in a reduced state, 30 minutes later and it still is not present in connect when selecting the folder, this is not an improvement in speed.