Photoshop CC slow in performance on big files

Hello there!
I've been using PS CS4 since release and upgraded to CS6 Master Collection last year.
Since my OS broke down some weeks ago (RAM broke), i gave Photoshop CC a try. At the same time I moved in new rooms and couldnt get my hands on the DVD of my CS6 resting somewhere at home...
So I tried CC.
Right now im using it with some big files. Filesize is between 2GB and 7,5 GB max. (all PSB)
Photoshop seem to run fast in the very beginning, but since a few days it's so unbelievable slow that I can't work properly.
I wonder if it is caused by the growing files or some other issue with my machine.
The files contain a large amount of layers and Masks, nearly 280 layers in the biggest file. (mostly with masks)
The images are 50 x 70 cm big @ 300dpi.
When I try to make some brush-strokes on a layer-mask in the biggest file it takes 5-20 seconds for the brush to draw... I couldnt figure out why.
And its not so much pretending on the brush-size as you may expect... even very small brushes (2-10 px) show this issue from time to time.
Also switching on and off masks (gradient maps, selective color or leves) takes ages to be displayed, sometimes more than 3 or 4 seconds.
The same with panning around in the picture, zooming in and out or moving layers.
It's nearly impossible to work on these files in time.
I've never seen this on CS6.
Now I wonder if there's something wrong with PS or the OS. But: I've never been working with files this big before.
In march I worked on some 5GB files with 150-200 layers in CS6, but it worked like a charm.
SystemSpecs:
I7 3930k (3,8 GHz)
Asus P9X79 Deluxe
64GB DDR3 1600Mhz Kingston HyperX
GTX 570
2x Corsair Force GT3 SSD
Wacom Intous 5 m Touch (I have some issues with the touch from time to time)
WIN 7 Ultimate 64
all systemupdates
newest drivers
PS CC
System and PS are running on the first SSD, scratch is on the second. Both are set to be used by PS.
RAM is allocated by 79% to PS, cache is set to 5 or 6, protocol-objects are set to 70. I also tried different cache-sizes from 128k to 1024k, but it didn't help a lot.
When I open the largest file, PS takes 20-23 GB of RAM.
Any suggestions?
best,
moslye

Is it just slow drawing, or is actual computation (image size, rotate, GBlur, etc.) also slow?
If the slowdown is drawing, then the most likely culprit would be the video card driver. Update your driver from the GPU maker's website.
If the computation slows down, then something is interfering with Photoshop. We've seen some third party plugins, and some antivirus software cause slowdowns over time.

Similar Messages

Adobe Photoshop CS3 collapse each time it load a big file

I was loading a big file of photos from iMac iPhoto to Adobe Photoshop CS3 and it keep collapsing, yet each time I reopen photoshop it load the photos again and collapse again. is there a way to stop this cycle?

I don't think that too many users here actually use iPhoto (even the Mac users)
However, Google is your friend. A quick search came up with some other non-Adobe forum entries:
.... but the golden rule of iPhoto is NEVER EVER MESS WITH THE IPHOTO LIBRARY FROM OUTSIDE IPHOTO.In other words, anything you might want to do with the pictures in iPhoto can be done from *within the program,* and that is the only safe way to work with it. Don't go messing around inside the "package" that is the iPhoto Library unless you are REALLY keen to lose data, because that is exactly what will happen.
.....everything you want to do to a photo in iPhoto can be handled from *within the program.* This INCLUDES using a third-party editor, and saves a lot of time and disk space if you do this way:
1. In iPhoto's preferences, specify a third-party editor (let's say Photoshop) to be used for editing photos.
2. Now, when you right-click (or control-click) a photo in iPhoto, you have two options: Edit in Full Screen (ie iPhoto's own editor) or Edit with External Editor. Choose the latter.
3. Photoshop will open, then the photo you selected will automatically open in PS. Do your editing, and when you save (not save as), PS "hands" the modified photo back to iPhoto, which treats it exactly the same as if you'd done that stuff in iPhoto's own editor and updates the thumbnail to reflect your changes. Best of all, your unmodified original remains untouched so you can always go back to it if necessary.

I've doubled my RAM but still can't save big files in photoshop...

I have just upgraded my Ram from the shipped 4GB to 8GB but I still can't save big images in photoshop. It seems to have made no difference to the speed of general tasks and saving and I can't save big files in photoshop at all. I already moved massive amounts of files off my computer and onto my external hard drive, so there is much less in my computer now, and twice the RAM but it is making no noticeable difference. When I click memory, under 'about my mac' it shows that the RAM is installed and now has twice the memory. Could this be something to do with photoshop? I'm running CS6.

Also, I just calculated 220 cm into inches and this is roughly 86.5 inches. Over 7 feet in length.
WIth an image that large, you may want to consider down sampling to a lower DPI to help with being able to work on and process images of this size much easier and it will be easier for your Print house to process, as well.
You might want to consider working with these rather large images at 225 DPI instead of 300 if resolution at close distances is still a concern.
Or what you good try is working with the images at 300 DPI, but then save them/export them as a Jpeg image at the highest image quality setting.
I do a lot of project where I use a high resolution jpeg image to save on image proceesing overhead.
The final printed images still come out pretty clear, clean and crisp without having to process those large files at a print house or having to deal with using that full resolution image in a page layout or illustration program.

Photoshop CC 2014 extremely slow after fresh intallation on MacBook Pro Late 2011, i7 8 GB RAM, Photoshop CS 5.1 performance OK

Hi there,
I just installed Adobe Photoshop CC 2014 on my MacBook Pro Late 2011 with 8 GB RAM after already having installed CS 5.1 on my MacBook.
So I have both installed at the same time.
But: CS 5.1 is much faster! The first time opening CC 2014 was really shocking, because it was so laggy and still is, and I don't know why this is.
I didn't do any weird performance settings, neither did I change anything else. I open a document in CC 2014 and it takes nearly double the time
compared to opening the same document in CS 5.1.
And with CS 5.1 running the app Memory Clean tells me that i have 1.5 GB of free memory, with CC 2014 running my memory is completely in use.
Are there any tipps/tricks/issues with having both installed at the same time? Am I missing something that is leading to that specific performance
issue?
I would be glad if someone could help me, because otherwise I have to say that upgrading to CC 2014 and buying the CC license for one year
didn't turn out to be a good thing.
Thanks!

Nothing here?
The MacBook now has 16 GB RAM, but not much change. Photoshop CS 5.1 performance is great after splitting the PSD into 3 different ones, Photoshop CC 2014 still much slower.
Does anyone experience the same problems, especially with many groups / layers / smart objects?
And is it possible to get back the money for purchasing the yearly CC license when I'm not satisfied with the product?
Thank you.

I was loading a big file of photos from iPhoto to Adobe Photoshop CS3 and it keep collapsing, yet each time I reopen photoshop it load the photos again and cal laps again. is there a way to stop this cycle?

I was loading a big file of photos from iPhoto to Adobe Photoshop CS3 and more then midway it keep collapsing, yet each time I re-open photoshop to load a small amount of photos, it load the previous photos again, and again it collapse. is there a way to stop this cycle and start a new?

http://helpx.adobe.com/photoshop.html

• Photoshop "action" doesn't work well for big file?

Hello -
I made a Photoshop® script (action) which works perfectly…
(Open .PDF files in Photoshop®, to after save them as .JPG files into another folder)
The problem comes when I launch a batch process.
It takes a while to the computer to open the large .PDF files, and when a file is opened,
well it doesn't go through the whole script. In fact, Photoshop® already open the second file and so on.
Then without running the rest of the script/action
NB. I work with the CS5 version of Photoshop® (on Mac).
Thank you for any input.
Have a nice day…
- Dimitri

Hello Curt -
I work on a MacPRO 8core (4 years old) with 16GB of RAM.
I have a 300GB HD as "scratch disk" (almost empty)…
- Dimitri

Need help. I am running a 27 in imac with 16 gigs of ram. Photoshop runs really fast, except when opening files. It takes 5-10 minutes to open even a small file of 1 meg. I cleaned and validated all the fonts and removed all questionable fonts. Reset pref

Need help. I am running a 27 in imac with 16 gigs of ram. Photoshop runs really fast, except when opening files. It takes 5-10 minutes to open even a small file of 1 meg. I cleaned and validated all the fonts and removed all questionable fonts. Reset preferences and still have problem. Slow to open and in force quit "Photoshop not responding" At this point should I uninstall and start over.

What are the performance Preferences?

PLEASE HELP! Aperture becomes MISERABLY slow after performing perfectly.

Posting on this forum is my absolute last resort, but I am absolutely desperate.
I am a professional photographer who works on Aperture for hours daily. I made the switch to Aperture from a Bridge-based workflow a few months ago. Ever since I started importing all of my past work into Aperture, I have been dealing with radically inconsistent performance which is, literally, causing me days of delays, and thousands of dollars in missed work.
*Here is how I am set up.* All of my images are being referenced on a WD My Book via FireWire 800 connection directly to my computer - no daisy chaining. It is a 1TB drive, and it is referencing about 75,000 photos - mostly RAW. I did this to maintain a traditional file hierarchy incase I didn't have access to Aperture. My Aperture library folder is stored on my iMac's main HD. When I started using Aperture, I had an 20" iMac 2.4Ghz with 2GB RAM, and a Radeon 256MB video card - which definitely exceeds the minimum system requirements.
*When I first open up Aperture,* it runs beautifully. Quickly cycling though images, making snappy adjustments, exporting to Photoshop, and saving quickly. Absolutely everything I love it for. I would say after about 15-30 minutes of usage, the program slows to a near halt. Photoshop will slow down significantly, saving in Photoshop takes 30-45 seconds, and when I return to Aperture, images will load previews indefinitely, rendering adjustments useless without finagling. If I get adjustments to load, the adjustments are choppy and inconsistent. Exporting takes forever. Switching from project folders, creating galleries, changing viewing parameters - all unacceptably slow. It absolutely sabotages the performance of my computer. I end up having to completely restart the program to reacquire those glorious 15-30 minutes. This is all so strange considering initially, the program runs as it should! Perfectly! It is not that my computer isn't up to Aperture's specifications, or it would be slow(er) from launch.
*This is what I have done so far.* I initially checked the consistency of the Aperture library, as well as rebuilt the library (several times). This caused no improvement. I then contacted Apple via phone support which proved useless. I am convinced the support techs are doing nothing more than reading troubleshooting dialogue from the website, because we got nowhere. I then brought my iMac and external HD into the Apple Store to show them specifically what I was experiencing. After talking to a rather snippy store employee who gave me circular answers and then suggested that I "just return it," I requested the manager. He was pleasant, and kind enough to suggest a RAM upgrade, and provide it for free. I then had 4GB RAM, and considering I didn't have an opportunity to play with it more than 20 minutes in the store, I left hoping that would be the solution.
After getting back to my office and spending a considerable amount of time in the program, I saw that little progress was made. Yes, performance was certainly faster, especially for those 15-30 minutes, but the same problem resurfaced.
I suspected that it may be my WD external HD, considering I had loaded it's software after purchasing it. I suspected that considering it does have a sleep mode, an auto-off mode and a "capacity gauge," it may have gone into sleep mode as I was working on a file, and had to "wake up" when trying to save it, causing the workflow to go haywire. I proceeded to uninstall all of my WD software. I checked the drive's consistency, and I checked for errors via several high-end drive repair and recovery programs, and it was operating perfectly.
Even after this, I am still experiencing the SAME problem, and I am at a stand-still with NO idea what to do.
PLEASE! I am begging for any assistance. I can't work like this, and I can't bear switching to another (inferior) workflow.
Thank you!!

Hi
I couldn't help feeling sympathetic to your situation. I dont wish to state the obvious, but have you done all the basic checks...Is this thread any help..
http://discussions.apple.com/message.jspa?messageID=8093761#8093761
Updating to the latest version 10.5.4 could be a help. There is a new update available now 10.5.5 but I choose to let it settle down personally before I add it. Look at the forums and follow its progress before installing.
Hope you get things resolved...

How to read big files

Hi all,
I have a big text file (about 140MB) containing data I need to read and save (after analysis) to a new file.
The text file contains 4 columns of data (so each row has 4 values to read).
When I try to read all the file at once I get a "Memory full" error messags.
I tried to read only a certain number of lines each time and then write it to the new file. This is done using the loop in the attached picture (this is just a portion of the code). The loop is repeated as many times as needed.
The problem is that for such big files this method is very slow and If I try to increase the number of lines to read each time, I still see the PC free memory decending slowly at the performance window....
Does anybody have a better idea how to implement this kind of task?
Thanks,
Mentos.
Attachments:
Read a file portion.png ‏13 KB

Hi Mark & Yamaeda,
I made some tests and came up with 2 diffrenet aproaches - see vis & example data file attached.
The Read lines aproach.vi reads a chunk with a specified number of lines, parses it and then saves the chunk to a new file.
This worked more or less OK, depending on the dely. However in reality I'll need to write the 2 first columns to the file and only after that the 3rd and 4th columns. So I think I'll need to read the file 2 times - 1st time take first 2 columns and save to file, and then repeat the loop and take the 2 other columns and save them...
Regarding the free memory: I see it drops a bit during the run and it goes up again once I run the vi another time.
The Read bytes approach reads a specified number of bytes in each chunk until it finishes reading all the file. Only then it saves the chunks to the new file. No parsing is done here (just for the example), just reading & writing to see if the free memory stays the same.
I used 2 methods for saving - With string subset function and replace substring function.
When using replace substring (disabled part) the free memory was 100% stable, but it worked very slow.
When using the string subset function the data was saved VERY fast but some free memory was consumed.
The reading part also consumed some free memory. The rate of which depended on the dely I put.
Which method looks better?
What do you recommand changing?
Attachments:
Read lines approach.vi ‏17 KB
Read bytes aproach.vi ‏17 KB
Test file.txt ‏1 KB

Photoshop crashes when opening more than 10 files at once

CS4 crashes when I open too many files at once. Like more than 10. They're not even very big files.

What are Your Photoshop – Preferences – Performance-settings?
Other than that You might consider doing OS-maintenance, like repairing permissions, cleaning PRAM etc. and trashing Photoshop-prefs … all of which might or might not help.

Why my quick selection tool on photoshop is slow on my mac

why my quick selection tool on photoshop is slow on my mac

BOILERPLATE TEXT:
Note that this is boilerplate text.
If you give complete and detailed information about your setup and the issue at hand,
such as:
exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
your settings in Photoshop > Preference > Performance
the type of file you were working on,
machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
what troubleshooting steps you have taken so far,
what error message(s) you receive,
if having issues opening raw files also the exact camera make and model that generated them,
if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
A screen shot of your settings or of the image could be very helpful too,
etc.,
someone may be able to help you (not necessarily this poster, who is not a Windows user).
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Thanks!

Problem with Photoshop CS6. If I open a file using Camera RAW

I have a new problem with Photoshop CS6. If I open a file using Camera RAW, and process it as usual, CS6 doesn't want to save it the way it used to. I don't know if I changed something by accident or not.
Here's what happens now: After opening from ACR to CS6 and completinhg all of my work, I choose "Save as..." The save as window opens showing the file name and format. The default format seems to be .PSD. I use the drop down to select .jpg. The file saves normally as a .jpg. When I go to close the image from, I get a new prompt asking, "Save changes to Adobe Photoshop document DSC_xxxx.NEF before closing?
I looked up at the file name in the bar above the work space and noticed that it does NOT change from "DSC_xxxx.NEF" to "DSC_xxxx.jpg" after I have saved the file as a .jpg,in my webesite but it always used to do that. This adds a few extra steps when closing a document and it really slows me down.
In fact, I wouldn't swear to this, but I think it used to save to .jpg by default, without me specifying this.
I don't see a setting in the preferences for what to use as the default file format for saving, so I don't know where to change it back.
Any ideas?
Thanks in advance

You are in the wrong forum; You actually need Photoshop forum at this link:
<http://forums.adobe.com/community/photoshop?view=discussions>
Hope you can repost your question at the correct link.

How do i open a VERY big file?

I hope someone can help.
I did some testing using a LeCroy LT342 in segment mode. Using the
Labview driver i downloaded the data over GPIB and saved it to a
spreadsheet file. Unfortunately it created very big files (ranging from
200MB to 600MB). I now need to process them but Labview doesn't like
them. I would be very happy to split the files into an individual file
for each row (i can do this quite easily) but labview just sits there
when i try to open the file.
I don't know enough about computers and memory (my spec is 1.8GHz
Pentium 4, 384MB RAM) to figure out whether if i just leave it for long
enough it will do the job or not.
Has anyone any experience or help they could offer?
Thanks,
Phil

When you open (and read) a file you usually move it from your hard disk (permanent storage) to ram. This allows you to manipulate it in high speeds using fast RAM memory, if you don't have enough memory (RAM) to read the whole file, you will be forced to use virtual memory (uses swap space on the HD as "virtual" RAM) which is very slow. Since you only have 384 MB of RAM and want to process Huge files (200MB-600MB) you could easily and inexpensively upgrade to 1GB of RAM and see large speed increases. A better option is to lode the file in chunks looking at some number of lines at a time and processing this amount of data and repeat until the file is complete, this will be more programming but will allow you to use much lass RAM at any instance.
Paul
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

Screen flickers and photoshop becomes slow

Hi,
I have been using photoshop for quite a while now and have never faced any issues until now. I upgraded from windows 7/64 bit to windows 8.1/64 bit and the problems have started. When I turn on the ruler view my ruler flickers and also the photoshop becomes slow. If I hold the spacebar(hand tool) and want to move to some area it's not smooth. When the ruler view is turned off it's all fine but as a web designer I can't do without the ruler. Earlier I had the whole screen flickering issues but I did some search on the internet and have tuned the drawing board to basic and that has solved the issue but not the ruler flickering issue. BTW I am using Photoshop CC. I am unable to work on it and I need some help please help me guys.
Thank you
Here is my system configuration
Dell Inspiron 15R N5110
Windows 8.1 x64
RAM 4gb ddr3
Intel 3000 Hd
Nvidia GeForce GT 525M
HDD 500gb

Here is my system info and no I cannot disable my onboard intel graphic as there is no option in bios.
Adobe Photoshop Version: 14.2 (14.2 20131211.r.515 2013/12/11:23:00:00) x64
Operating System: Windows 8 64-bit
Version: 6.2
System architecture: Intel CPU Family:6, Model:10, Stepping:7 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
Physical processor count: 2
Logical processor count: 4
Processor speed: 2395 MHz
Built-in memory: 4003 MB
Free memory: 1819 MB
Memory available to Photoshop: 3311 MB
Memory used by Photoshop: 57 %
Image tile size: 1024K
Image cache levels: 6
Font Preview: Medium
TextComposer: Latin
Display: 1
Display Bounds: top=0, left=0, bottom=768, right=1366
OpenGL Drawing: Enabled.
OpenGL Allow Old GPUs: Not Detected.
OpenGL Drawing Mode: Basic
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
AIFCoreInitialized=1
AIFOGLInitialized=1
OGLContextCreated=1
NumGPUs=1
gpu[0].OGLVersion="3.0"
gpu[0].MemoryMB=0
gpu[0].RectTextureSize=16384
gpu[0].Renderer="GeForce GT 525M/PCIe/SSE2"
gpu[0].RendererID=0
gpu[0].Vendor="NVIDIA Corporation"
gpu[0].VendorID=0
gpu[0].HasNPOTSupport=1
gpu[0].DriverVersion="?"
gpu[0].Driver="?"
gpu[0].DriverDate="?"
gpu[0].CompileProgramGLSL=1
gpu[0].TestFrameBuffer=1
gpu[0].OCLPresent=1
gpu[0].OCLVersion="1.1"
gpu[0].CUDASupported=1
gpu[0].CUDAVersion="6.0.1"
gpu[0].OCLBandwidth=2.48346e+010
gpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.40 NVIDIA via Cg compiler"
gpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[16384]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
gpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
gpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
gpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
gpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1
gpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1
gpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1
Application folder: C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\
Temporary file path: C:\Users\[myUsername]\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
F:\, 100.0G, 72.7G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\Required\Plug-Ins\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\Plug-ins\
Installed components:
   ACE.dll   ACE 2013/10/29-11:47:16   79.548223   79.548223
   adbeape.dll   Adobe APE 2013/02/04-09:52:32   0.1160850   0.1160850
   AdobeLinguistic.dll   Adobe Linguisitc Library   7.0.0
   AdobeOwl.dll   Adobe Owl 2013/10/25-12:15:59   5.0.24   79.547804
   AdobePDFL.dll   PDFL 2013/10/29-11:47:16   79.508720   79.508720
   AdobePIP.dll   Adobe Product Improvement Program   7.0.0.1786
   AdobeXMP.dll   Adobe XMP Core 2013/10/29-11:47:16   79.154911   79.154911
   AdobeXMPFiles.dll   Adobe XMP Files 2013/10/29-11:47:16   79.154911   79.154911
   AdobeXMPScript.dll   Adobe XMP Script 2013/10/29-11:47:16   79.154911   79.154911
   adobe_caps.dll   Adobe CAPS   7,0,0,21
   AGM.dll   AGM 2013/10/29-11:47:16   79.548223   79.548223
   ahclient.dll    AdobeHelp Dynamic Link Library   1,8,0,31
   aif_core.dll   AIF   5.0   79.534508
   aif_ocl.dll   AIF   5.0   79.534508
   aif_ogl.dll   AIF   5.0   79.534508
   AMTLib.dll   AMTLib (64 Bit)   7.0.0.169 BuildVersion: 7.0; BuildDate: Mon Apr 8 2013 2:31:50)   1.000000
   ARE.dll   ARE 2013/10/29-11:47:16   79.548223   79.548223
   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 2013/10/29-11:47:16   79.548223   79.548223
   BIBUtils.dll   BIBUtils 2013/10/29-11:47:16   79.548223   79.548223
   boost_date_time.dll   DVA Product   7.0.0
   boost_signals.dll   DVA Product   7.0.0
   boost_system.dll   DVA Product   7.0.0
   boost_threads.dll   DVA Product   7.0.0
   cg.dll   NVIDIA Cg Runtime   3.0.00007
   cgGL.dll   NVIDIA Cg Runtime   3.0.00007
   CIT.dll   Adobe CIT   2.1.6.30929   2.1.6.30929
   CITThreading.dll   Adobe CITThreading   2.1.6.30929   2.1.6.30929
   CoolType.dll   CoolType 2013/10/29-11:47:16   79.548223   79.548223
   dvaaudiodevice.dll   DVA Product   7.0.0
   dvacore.dll   DVA Product   7.0.0
   dvamarshal.dll   DVA Product   7.0.0
   dvamediatypes.dll   DVA Product   7.0.0
   dvaplayer.dll   DVA Product   7.0.0
   dvatransport.dll   DVA Product   7.0.0
   dvaunittesting.dll   DVA Product   7.0.0
   dynamiclink.dll   DVA Product   7.0.0
   ExtendScript.dll   ExtendScript 2013/10/30-13:12:12   79.546835   79.546835
   FileInfo.dll   Adobe XMP FileInfo 2013/10/25-03:51:33   79.154511   79.154511
   filter_graph.dll   AIF   5.0   79.534508
   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
   imslib.dll   IMSLib DLL   7.0.0.145
   JP2KLib.dll   JP2KLib 2013/10/29-11:47:16   79.248139   79.248139
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libiomp5md.dll   Intel(R) OMP Runtime Library   5.0
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   12.0
   LogSession.dll   LogSession   2.1.2.1785
   mediacoreif.dll   DVA Product   7.0.0
   MPS.dll   MPS 2013/10/29-11:47:16   79.535029   79.535029
   msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.8428
   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.8428
   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.8428
   msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   PatchMatch.dll   PatchMatch 2013/10/29-11:47:16   79.542390   79.542390
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CC   CC
   Plugin.dll   Adobe Photoshop CC   CC
   PlugPlugOwl.dll   Adobe(R) CSXS PlugPlugOwl Standard Dll (64 bit)   4.2.0.36
   PSArt.dll   Adobe Photoshop CC   CC
   PSViews.dll   Adobe Photoshop CC   CC
   SCCore.dll   ScCore 2013/10/30-13:12:12   79.546835   79.546835
   ScriptUIFlex.dll   ScriptUIFlex 2013/10/30-13:12:12   79.546835   79.546835
   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   4, 1, 2012, 1003
   tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   4, 1, 2012, 1003
   updaternotifications.dll   Adobe Updater Notifications Library   7.0.1.102 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   7.0.1.102
   WRServices.dll   WRServices Mon Feb 25 2013 16:09:10   Build 0.19078   0.19078
Required plug-ins:
   3D Studio 14.2 (14.2 x001)
   Accented Edges 14.2
   Adaptive Wide Angle 14.2
   Angled Strokes 14.2
   Average 14.2 (14.2 x001)
   Bas Relief 14.2
   BMP 14.2
   Camera Raw 8.0
   Camera Raw Filter 8.0
   Chalk & Charcoal 14.2
   Charcoal 14.2
   Chrome 14.2
   Cineon 14.2 (14.2 x001)
   Clouds 14.2 (14.2 x001)
   Collada 14.2 (14.2 x001)
   Color Halftone 14.2
   Colored Pencil 14.2
   CompuServe GIF 14.2
   Conté Crayon 14.2
   Craquelure 14.2
   Crop and Straighten Photos 14.2 (14.2 x001)
   Crop and Straighten Photos Filter 14.2
   Crosshatch 14.2
   Crystallize 14.2
   Cutout 14.2
   Dark Strokes 14.2
   De-Interlace 14.2
   Dicom 14.2
   Difference Clouds 14.2 (14.2 x001)
   Diffuse Glow 14.2
   Displace 14.2
   Dry Brush 14.2
   Eazel Acquire 14.2 (14.2 x001)
   Embed Watermark 4.0
   Entropy 14.2 (14.2 x001)
   Extrude 14.2
   FastCore Routines 14.2 (14.2 x001)
   Fibers 14.2
   Film Grain 14.2
   Filter Gallery 14.2
   Flash 3D 14.2 (14.2 x001)
   Fresco 14.2
   Glass 14.2
   Glowing Edges 14.2
   Google Earth 4 14.2 (14.2 x001)
   Grain 14.2
   Graphic Pen 14.2
   Halftone Pattern 14.2
   HDRMergeUI 14.2
   IFF Format 14.2
   Ink Outlines 14.2
   JPEG 2000 14.2
   Kurtosis 14.2 (14.2 x001)
   Lens Blur 14.2
   Lens Correction 14.2
   Lens Flare 14.2
   Liquify 14.2
   Matlab Operation 14.2 (14.2 x001)
   Maximum 14.2 (14.2 x001)
   Mean 14.2 (14.2 x001)
   Measurement Core 14.2 (14.2 x001)
   Median 14.2 (14.2 x001)
   Mezzotint 14.2
   Minimum 14.2 (14.2 x001)
   MMXCore Routines 14.2 (14.2 x001)
   Mosaic Tiles 14.2
   Multiprocessor Support 14.2 (14.2 x001)
   Neon Glow 14.2
   Note Paper 14.2
   NTSC Colors 14.2 (14.2 x001)
   Ocean Ripple 14.2
   Oil Paint 14.2
   OpenEXR 14.2
   Paint Daubs 14.2
   Palette Knife 14.2
   Patchwork 14.2
   Paths to Illustrator 14.2
   PCX 14.2 (14.2 x001)
   Photocopy 14.2
   Photoshop 3D Engine 14.2 (14.2 x001)
   Photoshop Touch 14.0
   Picture Package Filter 14.2 (14.2 x001)
   Pinch 14.2
   Pixar 14.2 (14.2 x001)
   Plaster 14.2
   Plastic Wrap 14.2
   PNG 14.2
   Pointillize 14.2
   Polar Coordinates 14.2
   Portable Bit Map 14.2 (14.2 x001)
   Poster Edges 14.2
   Radial Blur 14.2
   Radiance 14.2 (14.2 x001)
   Range 14.2 (14.2 x001)
   Read Watermark 4.0
   Reticulation 14.2
   Ripple 14.2
   Rough Pastels 14.2
   Save for Web 14.2
   ScriptingSupport 14.2
   Shake Reduction 14.2
   Shear 14.2
   Skewness 14.2 (14.2 x001)
   Smart Blur 14.2
   Smudge Stick 14.2
   Solarize 14.2 (14.2 x001)
   Spatter 14.2
   Spherize 14.2
   Sponge 14.2
   Sprayed Strokes 14.2
   Stained Glass 14.2
   Stamp 14.2
   Standard Deviation 14.2 (14.2 x001)
   STL 14.2 (14.2 x001)
   Sumi-e 14.2
   Summation 14.2 (14.2 x001)
   Targa 14.2
   Texturizer 14.2
   Tiles 14.2
   Torn Edges 14.2
   Twirl 14.2
   Underpainting 14.2
   Vanishing Point 14.2
   Variance 14.2 (14.2 x001)
   Variations 14.2 (14.2 x001)
   Water Paper 14.2
   Watercolor 14.2
   Wave 14.2
   Wavefront|OBJ 14.2 (14.2 x001)
   WIA Support 14.2 (14.2 x001)
   Wind 14.2
   Wireless Bitmap 14.2 (14.2 x001)
   ZigZag 14.2
Optional and third party plug-ins: NONE
Plug-ins that failed to load: NONE
Flash:
   Adobe Exchange
   Kuler
Installed TWAIN devices: NONE

Big File vs Small file Tablespace

Hi All,
I have a doubt and just want to confirm that which is better if i am using Big file instead of many small datafile for a tablespace or big datafiles for a tablespace. I think better to use Bigfile tablespace.
Kindly help me out wheather i am right or wrong and why.

GirishSharma wrote:
Aman.... wrote:
Vikas Kohli wrote:
With respect to performance i guess Big file tablespace is a better option
Why ?
If you allow me to post, I would like to paste the below text from my first reply's doc link please :
"Performance of database opens, checkpoints, and DBWR processes should improve if data is stored in bigfile tablespaces instead of traditional tablespaces. However, increasing the datafile size might increase time to restore a corrupted file or create a new datafile."
Regards
Girish Sharma
Girish,
I find it interesting that I've never found any evidence to support the performance claims - although I can think of reasons why there might be some truth to them and could design a few tests to check. Even if there is some truth in the claims, how significant or relevant might they be in the context of a database that is so huge that it NEEDS bigfile tablespaces ?
Database opening: how often do we do this - does it matter if it takes a little longer - will it actually take noticeably longer if the database isn't subject to crash recovery ? We can imagine that a database with 10,000 files would take longer to open than a database with 500 files if Oracle had to read the header blocks of every file as part of the database open process - but there's been a "delayed open" feature around for years, so maybe that wouldn't apply in most cases where the database is very large.
Checkpoints: critical in the days that a full instance checkpoint took place on the log file switch - but (a) that hasn't been true for years, and (b) incremental checkpointing made a big difference the I/O peak when an instance checkpoint became necessary, and (c) we have had a checkpoint process for years (if not decades) which updates every file header when necessary rather than requiring DBWR to do it
DBWR processes: why would DBWn handle writes more quickly - the only idea I can come up with is that there could be some code path that has to associate a file id with an operating system file handle of some sort and that this code does more work if the list of files is very long: very disappointing if that's true.
On the other hand I recall many years ago (8i time) crashing a session when creating roughly 21,000 tablespaces for a database because some internal structure relating to file information reached the 64MB hard limit for a memory segment in the SGA. It would be interesting to hear if anyone has recently created a database with the 65K+ limit for files - and whether it makes any difference whether that's 66 tablespaces with about 1,000 files, or 1,000 tablespace with about 66 files.
Regards
Jonathan Lewis

Photoshop CC slow in performance on big files

Similar Messages

Maybe you are looking for