Sounds like a plan. However I have a ZOTAC ZT-40503-10L GeForce GTS 450 (Fermi) 1GB 128-bit GDDR5 for the rebuild of the older PC. I uninstalled everything nVidia I could see then installed the GTS 450. Now Photoshop enables OpenGL Drawing by default and lists the nVidia details in the GPU Details section. However when I drag any window I see I'm dragging only the window outline, not the entire graphic of the window. Do you think I should still try my main PC's 9800 GT in the newer PC (PC2)?
I have been using the newer build to process proofs from photo sessions. There are usually 800-1000 images (from a Canon 5D MKII) after a shoot. I've been using ACDSee to quickly generate a Web gallery. Then I have a batch I run in Photoshop (after hitting Tab to clear the screen) to add a Proof stamp and do a little sharpening. Before "bulking up" PC2 to make it ready for main use the batch process would literally fly- about three images per second. All I could see on the screen was a flash of the original (Web-size) image and mostly the transparency mesh. I was afraid that when I started adding complexity to the PC the batch would slow down.
It did slow down. It runs about half as fast now. I can see each step in the batch process and never see the transparency checkerboard.
So..., I reinstalled the suspect 9800 GT card. Photoshop recognizes it, has OpenGL Drawing enabled by default and has the GPU details in the GPU Details box. I just could have re-seated the sucker! But dragging a window still only drags its outline.
But guess what? The batch runs at the slower speed like I described above for the GTS 450. It's got to be that I've given the computer more to do- like more services running in the background. I kind of suspected this would be the case. That's why I kept this newer PC "pristine" and didn't make it 'main" since last September because it was processing proofs so fast.
Maybe the newest build will run the batch really fast- until I load it up to make it main!
Thanks, - Dave
Honestly, I have not experienced a slowdown since my initial Windows 7 install, but then I have tweaked my Windows 7 setup a good bit. That may say something I tweak avoids the slowdown you're seeing. And I may know what...
One thing I often advise people to do is to disable Windows 7 Indexing. This virtually always frees up computer time and resources for your apps with very little downside (and even some upside).
Somewhere here I have a thread where I describe exactly how to do that. Basically it's a matter of stopping the indexing service, deleting the index, and setting a few other things so that they don't expect indexing to be available.
Since I'm not sure where that thread has gone, I'll reprint some tweaks from the "how to" guide I've put together in subsequent posts here... Give me a few minutes...
Indexing is supposed to make it quick and easy to find things on your computer using Windows Search (that little box at the upper-right of Explorer windows).
But when you think about it, does it make sense to read all the files on your disk, extract everything you could possibly want to search for, and store it on that same disk another way? To even consider indexing providing better performance than just searching the files, Microsoft must be picking and choosing the data they think you'll want to look for (excluding data you WON'T want to search for), where you'll want to search, and in what kinds of files, and in fact they are. How could they know everything you'll ever want to search for?
They can't. Not everything is indexed, and never will be!
Try this: Create a simple text file on your disk, in a temporary folder. Call it "FindMe.log" and put in the text "This file contains important tax information". Now navigate to that folder with Explorer and enter the word "tax" into the Search box at the upper-right. Enter any of the words in that file! Windows Search will not find the file, because it simply does not LOOK in .log files by default, and there's no fallback strategy - Windows Search simply does not index nor search for information for some kinds of files. Incredible!
All it takes is ONE TIME searching for something you know is there and NOT finding it to destroy your confidence in Windows Search.
And so they scan through your files endlessly, pick out the strings you might someday search for, and store them in yet another set of files (the "index"). As though your computer has nothing better to do.
Not only is the basic premise of this wrong, but it's not even implemented very well. The index often becomes corrupted, and so Microsoft has provided functions for you to clear and regenerate it. Just what you wanted to be doing - NOT.
Consider these shortcomings:
- Some file types are simply not indexed or searched by default – e.g., .log files, and there's no fallback. If you create a new file type no one's seen before, its contents will not be indexed.
- Only strings they think you are likely to search for are indexed.
- Because of poor implementation, indexing will miss things in some file types that are indexed – e.g., older Microsoft Word documents or files containing Unicode text (Microsoft's own invention).
- Indexes often become corrupted and the Windows Search results fall out of date or it stops finding things entirely.
- Indexing operations use computer time, increase disk wear, and interfere with your own access to your files.
In summary, indexed Windows Search operations in Windows 7 simply can't be trusted to find your data in your files when it's critical, and so they're essentially useless. Searching for filenames using Windows Search actually can be occasionally useful (though the syntax to ensure it searches only filenames is a bit tricky), but this doesn't require indexing.
Moreover, indexing can actually interfere with file operations, causing your system to report disk corruption, because of an implementation error in indexing and NTFS (search the web for "Atomic Oplock", for example).
So indexing should simply and utterly be disabled. This won't actually stop you being able to try Windows Search - on the contrary with indexing off Windows 7 will actually search your actual files (within the limitations listed above) just when you tell it to, and (since indexing isn't implemented very well) it may actually INCREASE the probability that you might find what you're looking for.
Here's how to disable indexing:
- Click Start and enter services in the search box.
- When Services (with little gears) comes up, click it.
- Scroll down to the Windows Search service.
- Right click it and choose Properties.
- Change the Startup type to Disabled.
- Click [ Stop ] to stop the service.
- Click [ OK ].
- Click Start and enter index in the search box.
- When Indexing options comes up, click it.
- Click the Advanced button.
- Click the [ Rebuild ] button to delete the index.
- It is a good idea to reboot after this.
So your searches work properly and you're not nagged by Windows to reenable indexing:
- Open a Windows Explorer window.
- Choose Tools – Folder Options.
- Click the Search tab.
- Click the button next to "Don't use the index when searching in file folders for system files (searches might take longer)".
- Click Start and type group policy into the search box.
- When Edit Group Policy comes up, click it.
- Navigate to User Configuration – Administrative Templates – Windows Components – Windows Explorer.
- Enable the Turn off Windows Libraries features that rely on indexed file data entry.
- If you do not have the Group Policy Editor on your version of Windows, change this registry entry:
DisableIndexedLibraryExperience = 1
Here's another performance tweak:
Improve Disk Cache Efficiency
Windows 7 does not enable one of its best features out of the box: The ability to cache disk writes in RAM then write the data to the disk as efficiently as it can.
Instead, Windows 7 runs with write-cache buffer flushing enabled by default. This essentially makes applications wait for the hard drive to finish writing their data before allowing them to continue, which slows things way down.
They probably don't enable this feature by default because you risk losing more data on a crash or power loss.
With this function disabled, however, and the full power of the disk cache brought to bear, the OS is free to batch together disk writes and schedule them to maximize throughput and minimize seeking. You will hear a physical difference as the drive will not seek nearly as much.
If your computer is stable and reliable, you have battery backup, and you have sufficient RAM, you can confidently disable write-cache buffer flushing to really speed disk writes up. Do this for each internal disk drive for which you want to speed up access.
To Turn Off Write-Cache Buffer Flushing
- Open an Explorer Window.
- Right click on your C: drive and choose Properties.
- Click the Hardware tab.
- Click on the physical hard drive for which you want to change the setting to highlight its name.
- Click the [ Properties ] button.
- Click the Policies tab.
- Check the box next to Turn off Windows write-cache buffer flushing on the device.
Speed Up NTFS File Access
When Windows accesses a directory or file on an NTFS volume, whether just for reading or not, it updates the "Last Accessed" time stamp. Since many files are typically accessed in a read-only fashion, this results in a lot more disk writes than you'd expect.
Very few programs rely on the "Last Accessed" time stamp, and if you don't personally plan to use it (via the Properties menu for a file or folder), then you can disable this update:
Execute this command:
fsutil behavior set DisableLastAccess 1
Alternatively, add or change this registry value, if it is not already set:
The Windows 7 file system also still generates old 8.3 format file names for each file you store on your disk. Unless you have old (ancient) applications that require 8.3 filenames, you can disable creation of the 8.3 format filename to increase performance a little more:
Execute this command:
fsutil 8dot3name set 1
Alternatively, add or change this registry value:
I hit s couple of snags. One is that nothing I type into Start/Search returns any results. Haven't we disabled this thing? In properties for the hard drives I have indexing turned off for each one. That wasn't in your tips. Should I enable it for C:\?
In regedit I don't see 'Explorer' in HKCU\Software\Policies\Microsoft\Windows\. Only 'Current Version'. I'm running Home Premium.
OK, I completed all the steps in "Disable Indexing" including creating "DisableIndexedLibraryExperience" with a value of 1 in HKCU\Software\Policies\Microsoft\Windows\Explorer. I restarted the PC. I still don't get any results in Start/Search on search terms like regedit or group policy. Let me know if you want dialog box screen shots.
I've completed 'Improve Disk Cache Efficiency'. I will now continue following your instructions with the two steps in 'Speed Up NTFS File Access'.
I've done the steps in Speed Up NTFS File Access using the Command Prompt. I went into regedit and verified that the keys and values are the way you show them. Your format, eg. "NtfsDisable8dot3NameCreation"=dword:00000001 is different than the way I see it in regedit but I
believe they are the same.
I ran my "proof stamp" batch again. It looks like I have my speed back. (Yay!) Maybe a little faster, like closer to four (Web-size) images per second. Photoshop still displays all the steps in the processing of each image rather than showing the transparency mesh most of the time, but the difference might be due to the re-seating of the 9800 GT card and the resulting additional functionality.
Many thanks! I will keep the "speed up my PC" instructions handy to use with my latest build.
Please let me know if you can think of steps I can take to get Start/Search to return results.
Oh, I believe you that you're not seeing the search results.
There's clearly something I've done that you have not - or a difference between Windows 7 Ultimate (which I'm running) and your version. I don't really believe the latter.
After having disabled indexing, did you delete the index? Start - Control Panel, [Advanced] button, then [Rebuild] (which clearly will only delete).
I'll be very curious to hear whether these tweaks boost your image generation process speed back up to what you saw before. I suspect the disk caching will help a lot.
I was anxious to report my results but for some reason I sat on my reply while I was doing other things. By the time I discovered my mistake I got my reply posted only a munite before your last one. I hope this puts us back in sync.
I did follow the instructions to delete the index via rebuild, but was not sure if it "took". I will repeat the steps and report back.
Noel, I went through all the steps in your tips again and I can't find where I"ve gone wrong. Still no results in Start>Search. When I do the Rebuild to delete the index, the list "Index these locations > Included Locations" is empty. Is that proof the index has been deleted?
When we stop the Windows Search service do we not stop search results from showing up in Start/Search?
Here is a screen shot of Folder Options > Search. Do have the settings right?
Thanks, - Dave
When we stop the Windows Search service do we not stop search results from showing up in Start/Search?
No, I promise. I would not stand for that.
In your Search tab that you've shown above, try setting the "Always search file names and contents (this might take several minutes).
This is what I have set:
If changing these settings doesn't work, I suspect there may have been a problem with that Explorer key you had to add to the Registry. Can you open that key and do a screen grab please? Maybe something's not quite right there. Here's what mine looks like:
I changed "What to search" in Folder Options > Search. Here is my DisableIndexedLibraryExperience screen:
How about if I run Microsoft's "Fix Windows Search when it crashes or is not showing results"? If it restores my search then I can go through your steps and see what it changed. If it restores indexing I could then go through your steps one at a time, rebooting and testing to see where the search stops working.
If the above doesn't work, I've some other information:
Open Regedit and look in this HKEY_CURRENT_USER key:
Look for these values:
Do they exist? If so, what are their values.
From what I've been reading, they should both be DWORD values of 0x00000002.
In the PC we're diagnosing the two keys are in \Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced with values of 1 and 0 respectively:
In my older PC I'm preparing to replace only Start_SearchFiles appears and that has a value of 2:
In \Software\Microsoft\Windows\CurrentVersion\Policies\ I have no 'Explorer' on either PC.
Eureka! I was cleaning up the Start Menu in a laptop after I signed off last night. Near the bottom of the Configure tree I saw radio buttons under 'Search other files and libraries'. So I fired the subject PC back up and sure enough, the radio button next to 'Don't search' was selected. I changed it to Search with public folders' and sure enough, I can not search in the Start/Search box! Not only that, but in the registry Start_SearchFiles now = 2 and Start_SearchPrograms
now = 1. So I wound up backing into your last instruction. All appears to be working.
I am forever grateful for the outside of Photoshop help! If you need any additional feedback please let me know.