Welcome to the forum.
Can you give us the full details of your I/O? You mention an SSD and a RAID, but more details might be useful, especially how you have them allocated, the RAID controller type, etc. The more, the better.
Also, details on your Source Footage, and your Sequence Preset could give someone some ideas.
You say that you have completely disabled Windows' Virtual Memory (Page File). Is that correct?
>page file disabled
You might want to search for page file articles at http://search.microsoft.com/search.aspx?mkt=en-US&setlang=en-US
I think you would do better to REDIRECT your page file to a drive other than your SSD, not disable it
Concerning the page file: As Premiere is consuming all RAM, my PC starts paging another 24 GB onto a HDD (in total than 50GB!). Since this HDD is not a SSD, the systems is becoming a snail then.
The other details: It is a intel raid 5. The sequence is 1080p. The clips are avchd 1080p/i and QuickTime 720p.
page file disabled
That is not possible. If no pagefile is found, Windows automatically creates a dynamic pagefile on your C: drive and everything you tried to achieve is made worse by Windows, by creating a dynamic one instead of a static one and by creating it on your C: drive, where you definitely do not want it.
An on-board Intel raid5 is slower than molasses in winter.
I don't agree. And I am sitting in front of the fast PC. As said at the beginning the Raid system is not heavliy used anyway and there are several posts concering slow loading of project. So this is not new.
Concerning the page file. Start google e.g. http://lifehacker.com/5426041/understanding-the-windows-pagefile-and-why-you-shouldnt-disa ble-it.
But why is the Premier Pro limitation not working?
We are having a Problem with RAM during playback or Scrubing in the Timeline the RAM use by CS6 starts to go up all the way to our 21 GB (asign to CS6) of the 24gb we have.. We are just viewing 30ss HD 1080P clips in the time coming form AE after color correcting and compositing of RED material.. The Memory Use of CS6 view in the Task Manager stays and it is not dump after hitting stop of the playback.. We have to quit CS6 to start playback again because it will start to skip frame and problems with audio when the memory starts to go up..
Media is on the Internal SATA Disk on the machine..
Our System is a BOXX
WS Dual Intel Xeon X5690 4.3Ghz Enhanced Performance Processors (Six−Core)
24GB DDR3−1333 REG ECC (8 − 2GB DIMMS)
NVIDIA Quadro 4000 2GB
250GB 7,200rpm SATA Drive
500GB 7,200rpm SATA Drive
Blackmagic Decklink SDI (using lattest driver 9.6.1) and yes we already updated and did not do anything to the RAM Problem.
Any hint of what maybe causing the problem?/
on your C: drive, where you definitely do not want it.
Actually, that's the best place to put the swap file, as once PP is loaded, the C: drive on a well tuned system isn't really being access much for anything else, so it's more "available" for the swap than any other drive in a production environment will be.
The only exception is if you have a dedicated drive for swap only, but really, who does that?
I was going to. But Eric talked me out of it. I was worried about wearing out the SSD. He said not to worry.
You are still forgetting the accesses by the OS for temp files, event viewer, logs, FAT tables, and the fact that your pagefile on the C: drive will never be placed on the fastest part of the disk. You can never avoid these accesses, but they always occur and thus there is always background activity on the C: drive even when PR is loaded.
I suppose I could activate my second SSD and see if putting the swap file on there instead of the C: drive would reduce my PPBM5 time by a second or two.
Maybe this weekend.
This problem has nothing to do with pagefile or hard disks. It's a typical memory leak caused by bugs in codecs. I had the same problem with wmv files using
Lavf54.3.100 WM encoding settings. Lavf53.6.0 is working well. Probably there is a bug in frame rate dubbling. Pagefile, FAT or anything like that has nothing to do with such memory leaks. Its a bug in encoding. Solution is to use an other program to encode video file with another settings without ffdshow libav Lavf54.3.100 filter.