Slow performance LR 1.3.1 (Library Module)

LR 1.2 is running OK on my iMac. A while ago I tried LR 1.3. The upgrade really slowed down performance. Mostly a lag in the sliders and navigation tools in both Library and Develop modules that made it unworkable to me. I changed back to LR 1.2.
Since I want to import Canon G9 RAW files into LR, I upgraded to LR 1.3.1 recently. Performance of sliders and the navigation tool in the Develop module seems the same as in LR 1.2 (or maybe even a little better). Which means it is OK (workable). It still shows the blur when navigating a 100% zoomed image though. But the navigation tool in the Library module still has the same slow performance as it had in LR 1.3. Unworkable!!! I tried everything: optimizing, new catalog, rendering previews, etc.
I need the Library module to work smoothly (as in LR 1.2) in order to compare images at 100% zoom. I am afraid I have to go back to LR 1.2 again and find another solution for my Canon G9 RAW files. Most inconvenient. I am very disappointed. Especially, since Adobe showed they CAN get it right with the Develop module in version LR 1.3.1...
Oh yeah, my system specs:
iMac 2.16 GHz Intel Core 2 Duo
3GB 667 Mhz DDR2 SDRAM (2GB + 1GB)
232,89 GB Harddrive, 113 GB available
ATI Radeon X1600 128MB
Mac OS 10.4.11
Please Adobe, make the Library module run as smoothly as the Develop module in version 1.3.2...

The preview folder is 2,11 GB big. The .lrcat is 47 MB big.
I opened a new test catalog. I imported 326 images. After the import I rendered 1:1 previews. It took a long time. Real memory used was between 700-1000MB. Virtual memory used was between 1000-1400MB. When it was done rendering it still keep on using 700MB real memory and 1000MB virtual memory. I had to close LR and restart. Real memory after restart was 75MB real memory and 375 virtual memory.
But it didn't matter. The lag in the navigation tool of the Library module was still there.
I noticed that when clicking in the navigation window there was less delay as when I slide the white square in the window (in Library module). In the develop module this seems the other way around. Sliding showed less delay than clicking.
What's going on here?
I also have a MacBook. Performance seems much faster than on my iMac overall. After creating a new catalog and rendering 1:1 previews, the lag in the navigation window seems less than before. But it was still there...

Similar Messages

Big Library:Slow Performance?

I have about 10,000 photos (.jpg ~3MB each) in my Aperture Library. I want to add many more photos but I'm worried about slow performance. My questions:
1. How big is your library or how big do you think the libraries can get?
2. Have you noticed slower performance with larger libraries?
3. Any opinion on breaking up into multiple smaller libraries vs. 1 larger library?

I am running two libraries,
one for all of my work related imagery, 15,000+ images 50/50 raw & jpegs and
the other for all of my stuff I shoot of sporting clubs, the bit I give back to the community, 18,000+ predominantly jpeg's
both run smoothly, one on the MacPro and the other on the G4 laptop.
Issue starts to be the backing up, if you are thinking it will get BIG, try a library for each client. Could be a good selling point as well, "your imagery is isolated from other clients and has its own dedicated backup".
Tony

Slow Performance with large library (PC)

I've been reading many posts about slow performance but didn't see anything addressing this issue:
I have some 40000 photos in my catalog and despite generating previews for a group of directories, LR still is very slow in scrolling through the pics in these directories.
When I take 2000 of these pics and import them into a new catalog - again generating previews, the scroll through the pics happens much much faster.
So is there some upper limit of recommended catalog size for acceptable performance?
Do I need to split my pics up by year? Seems counter productive, but the only way to see the pics at an acceptable speed.

I also have serious performance issues, and i don´t even have a large database catalog, only around 2.000 pictures, the db file itself is only 75 mb big. Done optimization - didn´t help. What i encountered is that the cpu usage of LR 1.1 goes up and STAYS up around 85% for 4-5 minutes after programm start - during that time, zooming in to an image can take 2-3 minutes! After 4-5 minutes, cpu usage drops to 0%, the background task (whatever LR does during that time!) has finished and i can work very smoothly. preview generation cannot be the problem, since it also happens when i´m working in a folder that already has all previews build, close LR, and start again instantly. LR loads and AGAIN i´ll have to wait 4-5 minutes untill cpu ussage has dropped so i can continue working with my images smoothly.
This is very annoying! I will stop using LR and go back to bridge/acr/ps, this is MUCH much faster. BUMMER!

Specific Problem with Library Module 1:1 Preview Loading

Hi everyone. I've spent hours searching Google & forums for specific tips to try but I've found nothing that solved my problem. I have a very specific problem loading 1:1 previews in Lightroom 3.3 while zoomed to 1:1.
When I initially import a shoot (usually 3000 to 6000 images), I always render 1:1 previews during import. My understanding is that this activity writes full-sized previews to the "Previews" folder, but I also have observed that .DAT files are created in the "Camera Raw Cache" folder. I have my Lightroom Previews folder and my Adobe Camera Raw Cache folder on the **same** solid-state hard disk, which is dedicated to Lightroom.
When I browse these newly-imported images in the Library module in Loupe view at 1:1 zoom, it's very zippy and fast to switch between images. The images load without any message at a lower resolution, and then "snap" to full resolution after 0.25 to 0.5 seconds. No "Loading" message appears.
However, once the previews have "sat around for a while", even if they are still supposedly available in the Previews folder, loading the image at 1:1 in Loupe as described takes 3-5 seconds. Shortly after going to an image, the message "Loading..." is displayed (it doesn't say where from), and 3-5 seconds later, the full res image appears.
This has nothing to do with changes to image settings requiring re-rendering of the preview. These are images that I've imported but haven't browsed in a while. I know that the previews are valid, because I can go to "Library > Previews > Render 1:1 Previews", and the task will complete within 20 or 30 seconds without re-rendering any photos after examining them and apparently finding that there are still valid 1:1 previews for all 4000 of them. After doing this "re-render," the slow loading behavior is the same as before, because the re-render process always completes without actually updating the previews that it found are already there and presumably decided were still valid. Discarding previews by "Library > Previews > Discard 1:1 Previews" and then trying to re-render them also does nothing, because LR3 apparently doesn't immediately delete the discarded previews, so they are picked back up again As-Is by the re-rendering process.
If I had to guess at the reason for this behavior based on the symptoms, I would say that it seems like Lightroom is forcing itself to re-render 1:1 previews upon browsing to images that are older than a certain age (very possibly the same "30 days" after which the 1:1 previews are supposed to be discarded).
Now, I've also observed that deleting the DAT files in the Camera Raw Cache folder has no adverse impact on load speed (which is what I would have expected to see if LR3 was looking for and loading images from this cache instead of the Previews folder).
What this means to me is that once the image previews reach this "outdated" state, I can't get fast 1:1 browsing performance in Loupe with any reliable procedure other than manually deleting [in Windows Explorer] the entire Preview folder and then re-rendering the 1:1 previews for this shoot. This is of course terribly inconvenient when there are recent previews that I want to save.
Note: I do not have any slowness under any circumstance when browsing at "Zoom to Fit". This is only a problem when I'm browsing at 1:1 zoom (like when I'm comparing sharpness between a set of photos).
Note: For images with the slow behavior described, once the image has been loaded once at 1:1 zoom, it's henceforth snappy again when returning to the image (as if Lightroom was once again accepting the Preview file as valid).
So, here's a summary:
Previews (X:\Lightroom Catalog Previews\) and Camera Raw Cache (X:\Lightroom Cache\) are on same, dedicated, fast drive
1:1 previews from recently-imported files load full-res at 1:1 zoom in less than 1/2 second.
Older 1:1 previews take 3-5 seconds to load full-res at 1:1 zoom, even though the previews are supposedly being loaded from still-valid 1:1 previews in the Previews folder.
I'm really tired, so i hope this makes sense. I don't see how this could be a hardware problem, because I get good performance with recently-imported images. I'm running LR3.3 on Win 7 Pro x64 with 8 GB of RAM and a 2.4 GHz Intel Core2 Quad CPU. Never had LR3 beta installed - upgraded to 3.0 from the last 2.X version. After upgrading, in response to this exact issue, I deleted my entire previews folder and rebuilt, but I continue to have the exact same problem on every shoot that I import. It's most noticeable on the large shoots, because I end up having to browse at 1:1 zoom to compare a set of similar images.
Only workaround I've found: in Windows Explorer, manually delete the Previews folder. Return to Lightroom and rebuild 1:1 previews. This forces the previews to be rebuilt for all images.
Another possible workaround I am going to experiment with: setting the Previews to "Do Not Discard", in case the defualt "Discard after 30 days" that I've used is causing or contributing to the problem. If Lightroom is actually discarding the images after 30 days but forgetting that it had discarded them when asked to re-render 1:1's, maybe setting to "Do not discard" will bandage that problem by never discarding them to begin with.
All right, I'm falling asleep at the keyboard. I'm afraid to add more details as they may become incoherent. Hope to hear some good news, as fixing this problem would make my LR3 experience so much more pleasant.
Can anyone assist with this problem?
- Tyson

function(){return A.apply(null,[this].concat($A(arguments)))}
Ian Lyons wrote:
The behaviour after previews have been around for a while (i.e. previews for unedited images) is not normal. There have been a few other reports of similar behaviour, but no real clues as to why it happens.
Yes - this is my problem. Previews should still be valid, and "Library > Previews > Render 1:1 Previews" says the images are still valid, but then Loupe rebuilds them anyways.
function(){return A.apply(null,[this].concat($A(arguments)))}
Ian Lyons wrote:
If everything was working correctly, the setting for discard shouldn't have any effect on whether the previews go stale or not. ...
My understanding is that if everything were working as intended, the "setting for discard" that I was referring to (Edit > Catalog Settings > File Handling > "Automatically Discard 1:1 Previews") should be the sole determinant of whether 1:1 previews must be rebuilt for images with unmodified settings.
For example, if I import an image and render a 1:1 preview, and if I set the "Auto Discard 1:1" setting to "30 Days", and if I make no changes to the image's settings, then I would expect that the image should render quickly (under 1/2 second) at 1:1 zoom in Loupe view for the next 30 days. On the 31st day, I would expect the image to take longer to load as a new 1:1 preview was rendered and stored, and then I would expect this new preview to be retained for another 30 days.
I would furthermore expect that the 30-day counter would be reset every time the image was re-rendered (i.e. if I go into Develop and change something).
To a certain extent, this is functioning correctly on my system. When I go to one of these "problem images" that inexplicably load slowly, returning to them subsequently is quick. I think my problem is just, as Rob suggested, that some part of Lightroom's "brain" has wacky ideas about whether an up-to-date 1:1 preview exists or not.
If I choose to "Never" automatically discard 1:1 previews (which is what I just switched to), then I should "Never" see unmodified images taking 3-5 seconds to "Load" at 1:1 zoom in Loupe.
Since I just nuked my Previews folder again last night and re-rendered 1:1's overnight for a 3000 image shoot, it might be a while before I start encountering this bug again. I will certainly post any further related experiences here and will keep checking for anyone who has further insight.
function(){return A.apply(null,[this].concat($A(arguments)))}
Ian Lyons wrote:
...we know that Lr3.4 RC fixed the manual discard bug, so, if I were you I would focus any further tests on Lr3.4RC.
Thanks for pointing this out. I will upgrade to 3.4RC - at least then I will be able to force a rebuild of previews from one shoot without having to manually delete the previews for my entire catalog. I'll no longer have to throw out all the food in the refrigerator just because something smells funny.
function(){return A.apply(null,[this].concat($A(arguments)))}
Ian Lyons wrote:
The DAT files are created at the same time as Library previews. However, they are only used in Develop module.
Yes, I definitely agree with this (although, the Cache is probably also used while rendering new previews after "Quick Develop" changes in the Library module....). I posted my observations to this effect just in case someone else wondered the same thing I did. It is clear that the DAT files get written every time a preview is rendered for RAW file. Rob, now that I'm thinking with a clearer mind, I think the only thing these Cached files are used for is if you "return" to recently rendered settings in Develop or Quick Develop - then, that particular combination of settings yields a match in the cache, and LR loads the image from the Cache into Previews and onto the screen. It is logical that the cache wouldn't help us when going to new settings, because the new settings would create a partially or completely different rendering than any other combination of settings. Adobe may be going to more advanced levels of "reusability" than this, but I'm sure this is the general state of things.
You may want to open back up write access to that Cache folder...
Thanks, Rob & Ian!
So, my question, or bug report, still remains for now - why am I biting into a bag of chips marked "Fresh" and finding them Stale? And why does it say "Paper Jam" when there is no paper jam?

Very, very slow performance

Lightroom's performance on my computer has become, at times, intolerably slow. After rebooting my iMac and not opening any other programs or browsers, it just took about eight minutes to import 23 files, and a few more minutes to build 1:1 previews. When things are running fine this might take one minute. (I always build 1:1 previews on import and this happens with recently imported files as well as older ones, so it's not a question of having to build previews on the fly.) I've had extremely slow performance ("Loading") just moving from one photo to another in the Library and Develop modules or moving from one module to another, typically up to about 90 seconds, or when LR is "preparing the file" for export or edit in PS. But not always -- sometimes it's quite zippy -- and there's no pattern that I can see. Generally when this is occurring, memory "pressure" and CPU usage are normal, but it happens when usage is minimal as well. Occasionally there is a spinning beach ball but not usually.
My catalog has about 30k photos and very few presets of any kind. Probably 75% of these files have never been edited at all. I don't make hundreds of local adjustment, rarely more than ten in one image. I have about 40 Smart Collections with an average of several hundred images each. I rarely use Smart Previews. I optimize and back up the catalog every time I exit LR, which is a few times a week. My file/folder structure is simple and clean: /Pictures/year/day.
I'm running LR 5.4 on a mid-2011 iMac, 3.4 GHz Intel Core i7, with 16GB of memory. I have the Lightroom catalog and previews on the main drive, which is a 250GB SSD with about 100GB free. (Problem happened when my catalog was on different internal drive, too.) My pictures folder is on an internal drive with over 100GB available. I have the maximum cache size set to 50GB. I'm running Mavericks but it was just as slow under Mountain Lion. It was just as slow in earlier versions of Lightroom, major and minor. Other programs/apps run just fine on my computer, including Photoshop. (Generally, LR's performance is the same whether or not PS is running.) The only performance issue I've noticed since switching to Mavericks is that Finder stalls for several seconds every once in a while.
I've seen this Lightroom problem referred to on various forums, including Adobe forums, for a long time now -- years -- and I've never seen a definitive fix. I think I've answered all of the questions that are usually asked. Is there any solution to this? I use LR 30-40 hours per week. I'm tearing my hair out and the option of moving to another program would be the very last resort, but I might have to do that.

I don't use your same workflow, and I assume you're shooting RAW. However, after I have built 1:1 previews in LR (which takes a LONG time), when I click on a file to decide if it's sharp or not, it still takes 5-10 seconds for each file to load. And my computer isn't slow, and I have the same issue on my laptop, which is new and fast. I haven't seen a satisfactory answer to this problem, nor much acknowledgement from Adobe. My files are from a Nikon D7100 with 24 megapixels, so the file size is likely a factor.
If you are shooting the type of subjects where you use 1:1 previews primarily to determine sharpness, you could consider Photo Mechanic (unfortunately it costs $150) as the first step in your workflow. It uses the embedded jpg files in the RAW file, so it loads 1:1 jpg previews almost instantly. Sports and nature photographers use this product all the time, mostly to delete losers.

Slow Performance - Java Related?

This is an old box that I bought used recently, but the system install is recent. The system performs very slowly - about 50% of the speed of comparable Mac's in the XBench database. If I use Xupport to manully run "All" of the system maintenance crons I get some improvement, but it quickly goes back to being slow.
Looking at my logs I have a "boat load" of Java errors under CrashReporter; there will be a string of "JavaNativeCrash_pidXXX.log" entries - many of them, as follows:
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : Bus Error occurred at PC=0x908611EC
Function=[Unknown.]
Library=/usr/lib/libobjc.A.dylib
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Many of the line entries that follow, but not all of them, refer to SargentD2OL, which is a Java app, which I installed, but it did not work properly so I removed it. Yet I continue to get Java errors that refer to this now non-existant app.
I have read that Java apps use a lot of resources, and that D2OL in particular uses a lot of resources. Can my slow performance problem be Java related? If so, any idea of how I can fix this problem?
G4 AGP Graphics Mac OS X (10.3.9) 500 MHz, 512M RAM

Sorry to take so long to respond, but other issues in life have demanded my attention.
None of the solutions given have had any affect. My Java folder has both a 1.3.1 and a 1.4.2 app - the Java Update 2 will not reinstall because it sees an up-to-date app in the folder. But reading the update file it says the older Java will be removed - but it is still there. Problem?
On XBench the system scores a 9 to 10, while similar boxes on the XBench database score around 18 to 20. My cpu, memory, and video scores are very low. The HD through-put scores are the only ones that are normal. TechTool Pro 4 finds no problems. I have removed the memory sticks one at a time and retested after each cycle - no difference.
I have two drives, each with a 10.3.9 install. One works fine, scores around a 17 on XBench, the other scores a 9 to 10. So it appears to be a software problem. The slower install is a drive from a iMac G3 that has been moved to the G4 - are there issues with this?
My favored drive is the prior G3 one (newer and faster than the other drive that system tests faster in XBench) - it has my profile and all my info on it. It worked fine in the G3 - no problems.
Thanks for the help,
G4 AGP Graphics Mac OS X (10.3.9) 500 MHz, 512M RAM, ATI 8500

Slow Performance, Windows with My Documents Redirection, path temp

I've been annoyed by the SLOW performace on Itunes for Windows ever since i purchased my iPhone, i think i know one reason for my slow performance now.
My Windowx-box is member of a domain (connected to a Windows Small Business server) and for security we use folder-redirection on "My Documents" folder (i.e instead of "C:\%username%\my documents\" we use \\server\%username%\my documents) this is a quite common setup on any businesscomputer using windows.
Itunes on windows defaults to storing its cache and library in My Documents and in my case its on \\server\ , this hurts performance tremendously since im on a wireless 54g connection.
I'd like to be able to configure where I want the library stored AND wich HD to put temp-files/cache on...
If this is something that takes ages to fix I welcome any reghacks or directions or wich file to hex-edit to make a workaround.

Copy the iTunes folder on the server to you local hard drive.
Hold Shift and launch iTunes.
Select *Choose library*.
Select the *iTunes library.itl* file in the iTunes folder on your local drive.

Extremely slow performance with Radeon HD 7870

Hi,
I am using a number of Adobe programs on my new Windows 8 64 bit system, with 16 gigs of ram, an Intel Core i5 2.67ghz, and AMD Radeon HD 7870 2 gig. All the programs (including After Effects and Illustrator) work very well with the exception of Photoshop CS6 64 bit, which has extremely slow performance with Use Graphics Processor enabled in my preferences (which Photoshop selects by default). If I turn off Use Graphics Processor, the slow performance vanishes. If I change Drawing Mode to Basic, there might be a slightly detectable improvement over Normal and Advanced, but it's still horribly slow. The refresh rate seems to be just a few frames per second. Everything is slow: brushes, zooming, panning, everything.
I've tried changing the settings I've seen suggested elsewhere: I switched Cache levels to 2, history states to 10, and tile size to 128k. No effect. Photoshop is currently at the default of using 60% of available ram. Efficiency has remained at 100% throughout all my tests. Also, this slow performance has affected me from the moment I installed Photoshop; it didn't crop up after previous good performance. The problem exists regardless of the size or number of documents I have open. Performance is still terrible even when I create a 500 x 500 pixel blank new canvas and try a simple task like drawing with the brush.
Photoshop is fully up to date, and so are my graphics drivers (Catalyst version 13.1). Any help would be greatly appreciated; at the moment performance is so bad in Photoshop that it's unusable with graphics acceleration enabled. Thanks in advance for replying.
Photoshop System Info:
Adobe Photoshop Version: 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00) x64
Operating System: Windows 8 64-bit
Version: 6.2
System architecture: Intel CPU Family:6, Model:14, Stepping:5 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2
Physical processor count: 4
Processor speed: 2665 MHz
Built-in memory: 16379 MB
Free memory: 13443 MB
Memory available to Photoshop: 14697 MB
Memory used by Photoshop: 60 %
Image tile size: 128K
Image cache levels: 2
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
OpenCL Version: 1.2 AMD-APP (1084.4)
OpenGL Version: 3.0
Video Rect Texture Size: 16384
OpenGL Memory: 2048 MB
Video Card Vendor: ATI Technologies Inc.
Video Card Renderer: AMD Radeon HD 7800 Series
Display: 1
Display Bounds: top=0, left=0, bottom=1080, right=1920
Video Card Number: 2
Video Card: AMD Radeon HD 7800 Series
Driver Version:
Driver Date:
Video Card Driver: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.d ll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Video Mode: 1920 x 1080 x 4294967296 colors
Video Card Caption: AMD Radeon HD 7800 Series
Video Card Memory: 2048 MB
Video Card Number: 1
Video Card: Microsoft Basic Render Driver
Driver Version: 9.12.0.0
Driver Date: 20121219000000.000000-000
Video Card Driver:
Video Mode:
Video Card Caption: Microsoft Basic Render Driver
Video Card Memory: 0 MB
Serial number: 90970078453021833509
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Temporary file path: C:\Users\RAFFAE~1\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
C:\, 931.5G, 534.8G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Additional Plug-ins folder: not set
Installed components:
   ACE.dll   ACE 2012/06/05-15:16:32   66.507768   66.507768
   adbeape.dll   Adobe APE 2012/01/25-10:04:55   66.1025012   66.1025012
   AdobeLinguistic.dll   Adobe Linguisitc Library   6.0.0
   AdobeOwl.dll   Adobe Owl 2012/09/10-12:31:21   5.0.4   79.517869
   AdobePDFL.dll   PDFL 2011/12/12-16:12:37   66.419471   66.419471
   AdobePIP.dll   Adobe Product Improvement Program   7.0.0.1686
   AdobeXMP.dll   Adobe XMP Core 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPFiles.dll   Adobe XMP Files 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPScript.dll   Adobe XMP Script 2012/02/06-14:56:27   66.145661   66.145661
   adobe_caps.dll   Adobe CAPS   6,0,29,0
   AGM.dll   AGM 2012/06/05-15:16:32   66.507768   66.507768
   ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56
   aif_core.dll   AIF   3.0   62.490293
   aif_ocl.dll   AIF   3.0   62.490293
   aif_ogl.dll   AIF   3.0   62.490293
   amtlib.dll   AMTLib (64 Bit)   6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00)   1.000000
   ARE.dll   ARE 2012/06/05-15:16:32   66.507768   66.507768
   AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
   AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
   Bib.dll   BIB 2012/06/05-15:16:32   66.507768   66.507768
   BIBUtils.dll   BIBUtils 2012/06/05-15:16:32   66.507768   66.507768
   boost_date_time.dll   DVA Product   6.0.0
   boost_signals.dll   DVA Product   6.0.0
   boost_system.dll   DVA Product   6.0.0
   boost_threads.dll   DVA Product   6.0.0
   cg.dll   NVIDIA Cg Runtime   3.0.00007
   cgGL.dll   NVIDIA Cg Runtime   3.0.00007
   CIT.dll   Adobe CIT   2.1.0.20577   2.1.0.20577
   CoolType.dll   CoolType 2012/06/05-15:16:32   66.507768   66.507768
   data_flow.dll   AIF   3.0   62.490293
   dvaaudiodevice.dll   DVA Product   6.0.0
   dvacore.dll   DVA Product   6.0.0
   dvamarshal.dll   DVA Product   6.0.0
   dvamediatypes.dll   DVA Product   6.0.0
   dvaplayer.dll   DVA Product   6.0.0
   dvatransport.dll   DVA Product   6.0.0
   dvaunittesting.dll   DVA Product   6.0.0
   dynamiclink.dll   DVA Product   6.0.0
   ExtendScript.dll   ExtendScript 2011/12/14-15:08:46   66.490082   66.490082
   FileInfo.dll   Adobe XMP FileInfo 2012/01/17-15:11:19   66.145433   66.145433
   filter_graph.dll   AIF   3.0   62.490293
   hydra_filters.dll   AIF   3.0   62.490293
   icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   image_compiler.dll   AIF   3.0   62.490293
   image_flow.dll   AIF   3.0   62.490293
   image_runtime.dll   AIF   3.0   62.490293
   JP2KLib.dll   JP2KLib 2011/12/12-16:12:37   66.236923   66.236923
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   12.0
   LogSession.dll   LogSession   2.1.2.1681
   mediacoreif.dll   DVA Product   6.0.0
   MPS.dll   MPS 2012/02/03-10:33:13   66.495174   66.495174
   msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6910
   msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6910
   msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6910
   msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CS6   CS6
   Plugin.dll   Adobe Photoshop CS6   CS6
   PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)   3.0.0.383
   PSArt.dll   Adobe Photoshop CS6   CS6
   PSViews.dll   Adobe Photoshop CS6   CS6
   SCCore.dll   ScCore 2011/12/14-15:08:46   66.490082   66.490082
   ScriptUIFlex.dll   ScriptUIFlex 2011/12/14-15:08:46   66.490082   66.490082
   svml_dispmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   12.0
   tbb.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   updaternotifications.dll   Adobe Updater Notifications Library   6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   6.0.0.24
   WRServices.dll   WRServices Friday January 27 2012 13:22:12   Build 0.17112   0.17112
Required plug-ins:
   3D Studio 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Accented Edges 13.0
   Adaptive Wide Angle 13.0
   Angled Strokes 13.0
   Average 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Bas Relief 13.0
   BMP 13.0
   Camera Raw 7.3
   Chalk & Charcoal 13.0
   Charcoal 13.0
   Chrome 13.0
   Cineon 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Clouds 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Collada 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Color Halftone 13.0
   Colored Pencil 13.0
   CompuServe GIF 13.0
   Conté Crayon 13.0
   Craquelure 13.0
   Crop and Straighten Photos 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Crop and Straighten Photos Filter 13.0
   Crosshatch 13.0
   Crystallize 13.0
   Cutout 13.0
   Dark Strokes 13.0
   De-Interlace 13.0
   Dicom 13.0
   Difference Clouds 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Diffuse Glow 13.0
   Displace 13.0
   Dry Brush 13.0
   Eazel Acquire 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Embed Watermark 4.0
   Entropy 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Extrude 13.0
   FastCore Routines 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Fibers 13.0
   Film Grain 13.0
   Filter Gallery 13.0
   Flash 3D 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Fresco 13.0
   Glass 13.0
   Glowing Edges 13.0
   Google Earth 4 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Grain 13.0
   Graphic Pen 13.0
   Halftone Pattern 13.0
   HDRMergeUI 13.0
   IFF Format 13.0
   Ink Outlines 13.0
   JPEG 2000 13.0
   Kurtosis 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Lens Blur 13.0
   Lens Correction 13.0
   Lens Flare 13.0
   Liquify 13.0
   Matlab Operation 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Maximum 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Mean 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Measurement Core 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Median 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Mezzotint 13.0
   Minimum 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   MMXCore Routines 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Mosaic Tiles 13.0
   Multiprocessor Support 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Neon Glow 13.0
   Note Paper 13.0
   NTSC Colors 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Ocean Ripple 13.0
   Oil Paint 13.0
   OpenEXR 13.0
   Paint Daubs 13.0
   Palette Knife 13.0
   Patchwork 13.0
   Paths to Illustrator 13.0
   PCX 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Photocopy 13.0
   Photoshop 3D Engine 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Picture Package Filter 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Pinch 13.0
   Pixar 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Plaster 13.0
   Plastic Wrap 13.0
   PNG 13.0
   Pointillize 13.0
   Polar Coordinates 13.0
   Portable Bit Map 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Poster Edges 13.0
   Radial Blur 13.0
   Radiance 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Range 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Read Watermark 4.0
   Reticulation 13.0
   Ripple 13.0
   Rough Pastels 13.0
   Save for Web 13.0
   ScriptingSupport 13.1.2
   Shear 13.0
   Skewness 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Smart Blur 13.0
   Smudge Stick 13.0
   Solarize 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Spatter 13.0
   Spherize 13.0
   Sponge 13.0
   Sprayed Strokes 13.0
   Stained Glass 13.0
   Stamp 13.0
   Standard Deviation 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   STL 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Sumi-e 13.0
   Summation 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Targa 13.0
   Texturizer 13.0
   Tiles 13.0
   Torn Edges 13.0
   Twirl 13.0
   Underpainting 13.0
   Vanishing Point 13.0
   Variance 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Variations 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Water Paper 13.0
   Watercolor 13.0
   Wave 13.0
   Wavefront|OBJ 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   WIA Support 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   Wind 13.0
   Wireless Bitmap 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00)
   ZigZag 13.0
Optional and third party plug-ins:
   DAZ Studio 3D Bridge 12.0
   DazUpdateScene 12.0
Plug-ins that failed to load: NONE
Flash:
   Mini Bridge
   Kuler
Installed TWAIN devices: NONE

Great news!
I followed your suggestion, Noel, and uninstalled my drivers with the Catalyst Uninstall Utility (which I hadn't used before), rebooted, reinstalled Catalyst 13.2 Beta 7, rebooted, deleted the PS Prefs, started PS, and now the performance is radically improved!
It baffles me why I would need to do a clean driver uninstall in a new system environment that has only ever had this video card, and is only a few months old, but that action seems to be what's improved the situation. Note that because I deleted the PS preferences, the good performance now occurs with the default Use Graphics Processor enabled, and Drawing Mode set to Advanced (with every feature in the Advanced dialog checked except 30bit display).
Having no reference point, I can't tell for sure if performance is as good as it theoretically ought to be for my system specs, but using the standard 13px brush is only slightly laggy behind the cursor, even if I become reckless and squiggle on the canvas violently. It wasn't just sluggish response before: Photoshop seemed to be in pain trying to draw the line segments as it laboured to catch up to the cursor. That is pretty much gone now.
Much more tellingly, zooming and panning the canvas is like it ought to be, responsive and clean, more or less like it was for me in CS4 with my old Nvidia 9600GT. The poor performance with zooming and panning was the most worrying aspect of the issue. It's a great relief to see these working more properly now.
I have to confess I'm a little embarrassed to have drug you through all this hassle only to discover that something as rudimentary as properly cleaning out the drivers would be the apparent solution. I never would have imagined that doing that, with such a new and stable system, would make any difference, since I don't have a legacy of older drivers dotting my hard drive. In any event, I'm really grateful that you guys took the time to try to help me.
In the interest of completeness, here's the relevant portion of my system info after doing the reinstall steps I mentioned above:
Adobe Photoshop Version: 13.1.2 (13.1.2 20130105.r.224 2013/01/05:23:00:00) x64
Operating System: Windows 8 64-bit
Version: 6.2
System architecture: Intel CPU Family:6, Model:14, Stepping:5 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2
Physical processor count: 4
Processor speed: 2665 MHz
Built-in memory: 16379 MB
Free memory: 13680 MB
Memory available to Photoshop: 14695 MB
Memory used by Photoshop: 60 %
Image tile size: 1024K
Image cache levels: 4
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
OpenCL Version: 3.0
OpenGL Version: 3.0
Video Rect Texture Size: 16384
OpenGL Memory: 2048 MB
Video Card Vendor: ATI Technologies Inc.
Video Card Renderer: AMD Radeon HD 7800 Series
Display: 1
Display Bounds: top=0, left=0, bottom=1080, right=1920
Video Card Number: 2
Video Card: AMD Radeon HD 7800 Series
Driver Version:
Driver Date:
Video Card Driver: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.d ll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Video Mode: 1920 x 1080 x 4294967296 colors
Video Card Caption: AMD Radeon HD 7800 Series
Video Card Memory: 2048 MB
Video Card Number: 1
Video Card: Microsoft Basic Render Driver
Driver Version: 12.100.17.0
Driver Date: 20130226000000.000000-000
Video Card Driver:
Video Mode:
Video Card Caption: Microsoft Basic Render Driver
Video Card Memory: 0 MB
As you can see, the Microsoft Basic Render Driver still appears as a Video Card in the list. This presumably has something to do with Windows 8, and I really don't know if its presence here is still a sign that my card is not being used to its optimal capability. I have a hunch that the slight lag that I am still experiencing with the brush when Use Graphics Processor is on -- totally absent with the acceleration turned off -- implies that Photoshop is still unable to take maximum advantage of my card. I would assume that the brush tool should be more responsive with acceleration on than off, in a rig without any issues, but that's just assumption on my part. If you turn off Use Graphics Processor on your systems, is the brush tool more or less responsive?
But again, panning the canvas with the hand tool is now extremely responsive, without any screen tearing or visible lag, and that's a massive improvement over the total meltdown of performance I was suffering from before.
Thanks again very much for your help. I'm grateful to all of you who took the time to chime in.

ITunes 10.1 (64-bit) slow performance

Hello all,
I have recently bought a new pc, a very fast machine (see details below), but I'm experiencing bad performance with iTunes 10.1 (64-bit) for windows.
I don't have a lot of stuff in iTunes, I have about 120 apps, 500 songs, 1200 photos, couple of ringtones and 0 videos in my library. The whole iTunes interface responds slowly. Like clicking on Music, Videos, my iPhone in the side menu makes iTunes freeze for a couple of seconds and then switches to the screen. Even after loading a screen iTunes is freezed for a seconds before it's responsive.
I've googled around for a while, and got some tips to disable some options in the preference window, so I've set all unnecessary things off, like: crossfadings songs, automatic update checking, looking for devices, automatic organizing, ping, genius, shared libraries, etc. but it doesn't speed up iTunes much.
It gets even worse whenever I connect my iPhone 3G (Fw 4.2.1, 16GB, Black). iTunes simply freezes for like half a minute and the pc makes a few beeping noises because of connecting an usb-device. Even Windows 7 slows down a lot while connecting. iTunes gets responsive once my iPhone appears under devices in the side menu.
Software I have constantly running in the backround are: AVG anti-virus free edition, SQL Server 2008, Steam and Skype. Turning off these softwares doesn't make a difference as well. There are no virusses or whatever on my pc. I let AVG anti-virus do a complete scan like once a week.
Taskmanager shows iTunes using about 240,000K of memory, followed by steam with 70,000k of memory and skype with 30,000k of memory.
Anyone else experiencing slow performance or know how to resolve this ?
System details:
Windows 7 64-bit
Intel i7 950 @ 3.06GHz quad core processor
6gigs of ddr3 (1600mhz) memory
Ocz vertex2 ssd (The O/S and all music, photos, apps are on this disk)
nvidia graphics card gtx460
Message was edited by: Leon49

Same with me! I recently bought a new laptop, and iTunes 9 was working just fine. It takes like 5 seconds to scroll down one line. Clicking on different tabs and things takes forever as well. I am not sure what is causing it yet, but like you, I have disabled all sorts of iTunes settings which has not helped yet. Hopefully Apple will fix this problem soon! Let me know if you find a way to solve this.
My PC Specs which are well above the minimum requirements:
Asus UL80Jt
Windows 7 64-Bit
Intel i3 330UM Dual Core Processor @ 1.2GHz (ASUS Overclocking to 1.7 GHz)
4GB RAM
1.3 GB Dedicated Video RAM
128 SSD

Powerbook painfully slow performance

Recently my powerbook has been running unusably slow. Here's a timeline:
- Noticed slow opening of applications, saving, switching from application to application, browsing folders through finder.
- Computer kept freezing after 1-10 minutes of use.
- Checked RAM in system profiler - 1GB RAM showing 512 MB.
- Removed RAM and restarted (new RAM being sent to me at present).
- Freezing problem stopped. Slow performance improved for 2-5 minutes after startup but after 10 minutes, back to same old slow usage.
- Checked hard drive, repaired permissions, did macjanitor cleanup.
- Hardware check from startup DVD showed no problems. SMART check OK'd hard drive.
- Archive and re-install tiger and updated to 10.4.9.
- Activity monitor shows %CPU usage as fairly normal. Kernel_task is using about 720MB of virtual memory under very light/no user usage.
- Created a new user and performance normal in new user, leading me to believe that the problem is related to user library and possibly preferences.
- Put preferences folder on desktop and started putting my preferences back into user library folder bit by bit, restarting and testing. The performance would be better each time but hard to test as I have to wait at least 10 mins to test each time - time consuming business.
Is there any way to narrow down which preference file is causing the problem without painstakingly re-adding preference files one by one to the user library folder, waiting 10 mins and testing?
Otherwise, could the diagnosis above be due to something else all together. Been through the discussions and can't get anything to work so far. The RAM was the cause of the freezing problem, but seems to have brought on the slowness problem.
Any help would be much appreciated, thanks Graeme.

Graeme:
If you have not done so recently run Unix Maintenance (CRON cleaning). Download and install MacJanitor and run all tests.
Dr. Smoke's FAQ Tuning Mac OS X Performance has some hints you may find helpful.
Regualar maintenance also helps performance. Take a look at the following articles:
Mac OS X 10.3/10.4: System maintenance
Macintosh OS X Routine Maintenance
Maintaining OS X
Good luck.
cornelius

Develop module & library module aren't matching

When I am editing, my photos look how I want them to in the develop module, but when I switch over to the library they look different. Some photos it doesn't apply the clarity, highlights, noise reduction, or sharpening. I haven't had this problem up until a month or two ago. It used to be the same between the two modules and I no problems editing. Now it's a pain to edit because I have to switch to the Library to see what the image is really looking like, go back to develop to try and change it, but cant end up getting it to look how I want. Images look the same zoomed in, but not in normal view. I am on Windows, Lightroom 3.6. I have tried reupdating the software, downloading an older version. also updated my video driver, and nothing helped. trying to avoid reinstalling all of lightroom because I do not want to lose any previewly modified images.
first one is the view from develop. you can tell its a lot more noisey.
second picture is from the library. it's a lot more smooth.
so basically my images aren't being shown correctly. I have looked through a lot of discussions on here and no one seems to have an answer...please help me! editing should be fun, not frustrating.

Rivosyke wrote:
Thanks for the response. This appears to be more the issue with image that is exported is using the algorithm for the library module as opposed to the changes made using the develop module. The histograms are different when switching between the two modules (Library/Develop) for the same image.
Camera: D7100
Image Type: RAW
ISO: 3200
Bingo! You're using an ISO 3200 image with fairly high sharpening settings, which is going to increase noise in the image. If you view the image at 1:1 in the Develop module the noise should very visible. The Develop module and Library module 1:1 previews should both show the noise and look very close to each other. The reason why less than 1:1 Zoom previews (i.e. Fit, Fill, 1:4) and histograms look different is explained in my reply #29 under this heading MORE THAN YOU PROBABLY NEED TO KNOW (For Techno Geeks & Nerds Only). The Export module uses the same Bicubic algorithm as the Library module, which is why the Library module's preview is more accurate than the Develop module. Virtually all image editors (not just LR) use the same Bicubic resizing algorithms and will produce the same discrepancy when compared to LR's Develop module preview.
Fortunately there is a very easy solution to this issue. Unfortunately many people prefer to complain, say it is a LR "bug," and don't listen further to suggestions on "fixing" the issue. If you fall into the latter camp don't bother reading further! Sorry if this sounds crass and cynical, but I can only provide advice. Whether you believe me and try it is your decision! It works for me using five different camera models with both raw and JPEG image files.
High ISO and/or High Sharpening Preview Discrepancy Fix
1) Set Develop module to 1:1 Zoom View.
2) a. Adjust Sharpening panel settings for desired look.
b. With noisy images it's best to keep the Detail setting no higher than 35.
c. Try using the Masking slider to reduce noise in even toned areas.
3) Increase Detail panel Color setting until the color noise is barely visible.
4) If there is still some residual color noise try increasing the Color detail setting to ~80.
4) Increase the Detail panel Luminance setting until noise is barely visible or gone.
5) If the image has lost significant sharpness try increasing the Luminance Detail setting to ~80.
6) If necessary go back to steps # 2-5 and make small adjustments to the Sharpening and NR settings.
Now compare the Develop and Library previews at Fit view or better yet at 1:8, 1:4, or 1:3. They should look very close to each other with the Develop preview very slightly sharper. Full-size and reduced size Exports should look very close to what you see in the Develop module. When Resizing images don't forget to add Export Output Sharpening. When images are Resized the Output Sharpening setting has more influence on image sharpness than the LR Develop Sharpening settings. For most images the Screen Standard setting should produce crisp images. If you want more try the High setting. I generally find the Screen Low setting produces the most natural look. YMMV dependent on lens performance, camera shake, focus issues, or simply poor lighting (cloudy, foggy, etc.).

Fonction HR_INFOTYPE_OPERATION very slow performance in bacth job

Hi all experts!
Does any one having a problem with slow performance while using the fonction HR_INFOTYPE_OPERATION and running in batch mode for a big population of data ?
I have tried to use
    nocommit         = 'X' as parameter in the fonction HR_INFOTYPE_OPERATION
and calling after each update.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        wait = 'X'.
And the performance is very long.
I also remarque that if we run for a small population like less than 500 employees then it finish within 20 mins. But If I ran for a polulation of 5000 employees then it take more than 6 hours = 3600 mins. ?
Thanks for your answer.
Hugo Nguyen

Call Function module 'HR_PSBUFFER_INITIALIZE' After each call to HR_INFOTYPE_OPERATION.
Refer [link|http://brookshireconsulting.com/technical_update.html] for more information.
I have tried it my own and it do improve the performance,.
Hope this improves the performace for you as well.
Regards
Shital

LR5 slow performance selecting images in Grid view

LR5 is noticeably slower than LR4 when CTRL-click selecting a group of images in Grid view in the Library module. There is frequently (but not always) a pause of up to a few seconds before an image will show as selected. Also, when I try to grab the selected images and drag and drop into a collection, the images will be deselected if I try this too quickly.
Nothing changed on the computer since the upgrade from LR4.
PC running Win7, 64 bit
i7 processor, 8G RAM
lots of HDD space
LR running off the C: drive
thanks
Bill

Trying ticking it and unticking it to see if it is stuck. It works fine on the two systems I've tested.

BC_MSG slow performance

I experience slow performance in a SAP PI 7.1EHP1 SP05 installation. The BC_MSG table contains about 550.000 messages. I archive and delete message that are 10 days old. The environment is Redhat Linux 5.5 64bit with 16GB RAM and oracle 10.2.0.4. 
 
The problem is when I want to query all message containg error in the last 7 days or more. It needs about 5 minutes to respond and sometimes more that ends with request timeout from ICM. I shrink the tables, rebuild the indexes, restart the system many times, apply latest service pack (SP06) but the performance remains unchanged. 
 
The query that is executed is the following: 
 
<pre>
SELECT "MSG_ID","DIRECTION","REF_TO_MSG_ID","CORRELATION_ID","SEQUENCE_ID",
"SEQUENCE_NBR","CONN_NAME","MSG_TYPE","STATUS","TO_PARTY_NAME",
"TO_PARTY_TYPE","FROM_PARTY_NAME","FROM_PARTY_TYPE","TO_SERVICE_NAME",
"TO_SERVICE_TYPE","FROM_SERVICE_NAME","FROM_SERVICE_TYPE","ACTION_NAME",
"ACTION_TYPE","DELIVERY_SEMANTICS","SENT_RECV_TIME","TRAN_DELV_TIME",
"SCHEDULE_TIME","PERSIST_UNTIL","TIMES_FAILED","RETRIES","RETRY_INTERVAL",
"MSG_PROTOCOL","TRANSPORT","ADDRESS","CREDENTIAL","TRAN_HEADER",
"VALID_UNTIL","NODE","ERROR_CODE","ERROR_CATEGORY","PP_USER","PP_HASH",
"VERS_NBR","VERS_WAS_EDITED","PRIORITY_TYPE","PRIORITY"
FROM
"BC_MSG" WHERE "BC_MSG"."MSG_ID" IS NOT NULL AND ("STATUS" = :1 OR "STATUS" =
 :2) AND "SENT_RECV_TIME" >= :3 AND "SENT_RECV_TIME" <= :4 ORDER BY 21 DESC
</pre>
 
Parameters: 
:1 = 'FAIL' 
:2 = 'NDLV' 
:3 = 2011-03-01 08:06:02.34 (example) 
:4 = 2011-03-02 08:06:02.34 (example) 
 
 
This statement is executed for each day for the time interval I specify (e.g. 7 days of the week if the interval is 'Last 7 Days'). I don't know why they don't use one SQL for the specified interval. 
 
When I enable trace in the Open SQL monitor the execution time I see is very disappointing, about 22 - 46 seconds for each query. I also enable SQL trace in Oracle database and the results I get are the following: 
 
<pre>
call count cpu elapsed disk query current rows
Parse 0 0.00 0.00 0 0 0 0
Execute 2 0.00 0.00 0 0 0 0
Fetch 2 10.74 79.70 50473 62752 0 6
total 4 10.74 79.70 50473 62752 0 6
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 32
Elapsed times include waiting on following events:
 Event waited on Times Max. Wait Total Waited
 Waited -
db file sequential read 50473 0.15 72.90
SQL*Net message to client 2 0.00 0.00
SQL*Net more data to client 1 0.00 0.00
SQL*Net message from client 2 0.00 0.00
</pre>
 
The 'db file sequential read' is what worries me but I don't know what to do. 
 
Also I tried the same query using Db Visualizer and the jdbc jar file. The response was much better and the execution plan was different as you can see in sql trace results: 
 
<pre>
call count cpu elapsed disk query current rows
Parse 1 0.01 0.01 0 0 0 0
Execute 1 0.00 0.00 0 0 0 0
Fetch 1 0.00 0.00 0 7 0 0
total 3 0.01 0.01 0 7 0 0
Misses in library cache during parse: 1
Optimizer mode: ALL_ROWS
Parsing user id: 32
Rows Row Source Operation
 0 SORT ORDER BY (cr=7 pr=0 pw=0 time=636 us)
 0 INLIST ITERATOR (cr=7 pr=0 pw=0 time=487 us)
 0 TABLE ACCESS BY INDEX ROWID BC_MSG (cr=7 pr=0 pw=0 time=459 us)
 0 INDEX RANGE SCAN I_BC_MSG_STATUS_SENT (cr=7 pr=0 pw=0 time=347 us)(object id 96079)
Elapsed times include waiting on following events:
 Event waited on Times Max. Wait Total Waited
 Waited -
SQL*Net message to client 2 0.00 0.00
SQL*Net message from client 2 0.18 0.19
</pre>
 
The I_BC_MSG_STATUS_SENT index that scans is the index using the columns STATUS, SENT_RECV_TIME I created to see if performance is better. 
 
Generally the system works fine. I handles 50.000 messages per day with no delays. But the monitoring performance is annoying. I need your expertise on that. 

You, also, have waaaay too many user startup/Login items.
You need to pare these down to the apps you really need to have launched at startup and running in the background.
Add or remove automatic items
Choose Apple menu > System Preferences, then click Users & Groups.
Select your user account, then click Login Items.
Do one of the following:
Click Add below the list on the right, select an app, document, folder, or disk, then click Add.If you don’t want an item’s windows to be visible after login, select Hide. (Hide does not apply to servers, which always appear in the Finder after login.)
Select the name of the item you want to prevent from opening automatically, then click Delete below the list on the right.
You need to make sure to update all of your third party software if there are OS X Mavericks updates that can be applied.
You may need to go the third party developers' websites if there are no updates through the Mac App Store.
Make sure all of your Web browser Internet plugins, extensions and add-ons are updated to recent versions, also.

Mac pro Slow Performance

Hello Everyone,
I made a similar post about this subject not to long ago but now im back in the same situation. I will just recap everything that i did and hear your guys thoughts on what i did.
So to make a long story short.. I have a 2009 imac that contains all of my applications that i use on a daily basis. I then bought a 2012 12-core Mac Pro. Instead of being patient i wanted to start using this machine right away. I then set up migration assistant on both machines and literally copied everything over from my imac to my newly purchased mac pro. I later realized that this was a bad idea because it brought over boat loads of crap that was not being used (essentially 700GB) My computer was running very slow, defiantly not at speed of what a 12-core should be running at. so i started cleaning it up to the best that i could and was able to clear up 200 or so GB's. I still was not satisfied by the results i was getting. I kept getting beach balls and slow performance overall. so i went out and bought a 120GB SSD drive and figured that would be my best solution... well certainly it was at first. I then cleaned up my applications folder to clear up room in that folder. so after that was done i used migration assistant to transfer JUST the APPLICATIONS over to the SSD. After that was complete i then received a ton of crap on on the SSD. On boot up im not getting a pop up that is attached to a program i use to have on the iMac and is started to run slower than before the migration to the SSD...
So basically this is where i stand. I am thinking about just starting over from scratch and only bring over the files and applications that i need on the SSD. What is the best way to take applications off of my imac and put them onto my mac pro (meaning without migration assistant) The reason i need to transfer them over is because i do not have all of the applications on CD form to just re-install again. However, if i need to get the applications from the CD's for this to work then i will just have tp go through with that extra bit of trouble to do it the right way.
The whole purpose of this is trying to clean up my computer and keep it as organized as possible.
If anyone has any recommendations for the best way to perform this operation, its greatly appreciated!
thanks in advance!

A clean install along with Setup Assistant (or Migration Assistant) really is good and important way to go.
Too many issues moving to a newer OS and it has been made easy.
You can CCC clone the home folders elsewhere.
You can CCC the system and apps to another drifve and retain just your home library (the part that is now hidden which is annoying to some and taking too invasive into user space as if we can't and don't need access?)
~/Library
The only apps you can are ones you may as well just download and mount and drag, the type that lack and don't need to install anything anywheres but the package of the app itself.

Slow performance LR 1.3.1 (Library Module)

Similar Messages

Maybe you are looking for