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?
Anyone?
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.
T.
We'll look onto this issue and see what's going on.
Tony Severenuk said: We'll look onto this issue and see what's going on. T.
Thanks for your consideration on this, Tony.
To answer your question in your comment on my blog post:
I don't think this is on the list to change with X7.1. CONNECT is working as designed, using the Windows Indexing Service to find the local content (just like the search box in Windows Explorer). The first time the indexing happens, it can slow down the system, but once the full indexing is done, the performance impact should be negligible. If you go to Control Panel > Indexing Options, you can specify what should get indexed, and if you reduce the number of folders / locations being monitored, it will also reduce the work on the OS.
I did have a problem once with the indexing service, and the solution was to go in the advanced options of that control panel setting, and rebuild the index. If you have an SSD and a normal HD, you can also change the location of the index file in the advanced options.
Gerard Metrailler said: To answer your question in your comment on my blog post: I don't think this is on the list to change with X7.1. CONNECT is working as designed, using the Windows Indexing Service to find the local content (just like the search box in Windows Explorer). The first time the indexing happens, it can slow down the system, but once the full indexing is done, the performance impact should be negligible. If you go to Control Panel > Indexing Options, you can specify what should get indexed, and if you reduce the number of folders / locations being monitored, it will also reduce the work on the OS. I did have a problem once with the indexing service, and the solution was to go in the advanced options of that control panel setting, and rebuild the index. If you have an SSD and a normal HD, you can also change the location of the index file in the advanced options.
Thanks for your response, however it is unacceptable, or you do not full understand the problem. If this is truly by design then it is an extremely poor one, under no circumstance is it acceptable for connect to force an index every time it is opened, windows should control this not connect. As it is now the indexer must run constantly and to add insult to injury you must wait for the index to finish before displaying the contents of the folder, this is ok if I am searching but not when I select a folder and expect to actually see the contents of it. Try this, go to windows explorer and add a new file to a folder, then open connect and select that folder and see if it is present, as you will see it is not, however, the indexer is fired up and you will need to wait until it has indexed that folder before it does. This is a horrible design don’t you think? This should behave the same way as windows explorer if a files exists in a folder it should exist in connect when selecting the same folder. How can one truly rely on connect to provide an accurate assessment of assets on their drive?
Thanks for your response, however it is unacceptable, or you do not full understand the problem.
If this is truly by design then it is an extremely poor one, under no circumstance is it acceptable for connect to force an index every time it is opened, windows should control this not connect.
As it is now the indexer must run constantly and to add insult to injury you must wait for the index to finish before displaying the contents of the folder, this is ok if I am searching but not when I select a folder and expect to actually see the contents of it.
Try this, go to windows explorer and add a new file to a folder, then open connect and select that folder and see if it is present, as you will see it is not, however, the indexer is fired up and you will need to wait until it has indexed that folder before it does. This is a horrible design don’t you think?
This should behave the same way as windows explorer if a files exists in a folder it should exist in connect when selecting the same folder. How can one truly rely on connect to provide an accurate assessment of assets on their drive?
Boomhauer said:under no circumstance is it acceptable for connect to force an index every time it is opened, windows should control this not connect.
Hi there, in X7.1, the indexing won't kick in for browsing anymore.
This is great news! Thanks for the update, Hendrik.