Temp File Placement

  • Thread starter Thread starter J Go
  • Start date Start date
J

J Go

New member
Hey folks! Where is it best to put the 2 temp files in CEP? I will be running a 40G WD HD on the primary master, which will hold programs and the OS, and an 80G WD HD as the Secondary Master for audio trtracking and storage. It recommends putting one of the temp files on a different drive as the first one, but would this degrade performance, writing to the same drive as the program is running off of?

Thanks in advance for any advice!
 
You should install CEP on the master drive, with the operating system and whatnot.

Make your 80gig drive the primary place for temp files, and your main drive as the secondary, though Im sure you wont be exhausting the 80gig without clearing your temp files


Peace
Chris
 
Thanks! So if I understand you correctly, the second temp file isn't used until the first one runs out of room?

Could I just not use the second temp file?
 
I think you can not declare a second temp space, but I'd go ahead and do it anyways.

There's thousands of people on this site who run everything off one drive (and its not 40gigs either)

-Chris
 
I'm running Cool without a second temp file - the temp file is on the same hard drive as the program.

The second hard drive is just for audio file storage/reading/writing.

I've never thought there was a better way to run it than this...

Well, is there? LOL
 
CEP recommends you use your largest drive for temp files, which in my case is my audio only drive.

So I've got temp files, audio files, and personal mp3s on drive J, and applications and documents on drive C


One of the dudes from syntrillium told me this was best.


-Chris
 
I reckon there's more than one way to skin a cat, so I'll just play with the no second temp file/2nd temp on audio drive/2nd temp on primary drive configs and see what works best. My largest drive will be the 80G secondary master, and the program running off the primary master.
Obekaybe, thanks for the input!
 
Don't know if this would necessarily apply to Cool Edit temp file setup.... but it might.....

Often when you setup a server (or workstation) it is preferrable to put the memory cache file on it's own partition. One of the reasons is that the large file can reside on sectors next to each other instead of being fragmented, because reading and writing fragmented files takes much longer than if the file is not very fragmented. With a large file such as disk cache, the file could easily become VERY fragmented and slow to access.

SO FOR COOL EDIT, I believe the temp files are the undo's for the destructive edits and such, which would be fairly large files. If this is the case, I would say you want your main temp file to be seperate (different drive or different partition) from where the OS resides--which is made of lots of little files that would cause fragmentation of the larger files. If you have a drive primarily consisting of fewer but larger files (as in audio files), I would think this is the best place for the temp file, so they would stay unfragmented.

Also, I would say it's important to defragment this drive on occasion for quick file access.

Also, my guess is that it doesn't matter which drive Cool Edit resides on, but for consistency, it should probably just go under c:\program files. Cool Edit is a farily small program, and probably loads completely into RAM before usage. Even if it doesn't all load when the app starts up, the seperate componants should load very, very quickly--in comparison to any of the wav files access times.



Hope that wasn't too much bs for everyone, and someone actually got something useful out of that rant....
 
One more thing about files and hard drives.....

A couple years ago I saw a RAID system for the PC. It just used a special IDE controller or something, but the other components were normal PC components. Don't know much about it, but it's supposed to be very, very fast. I think the original intent was for gaming, but boy would that make a killer audio workstation!!!
 
chrisjob - yeah, I know synt recommends putting the first temp file on the largest drive. And my largest drive is the drive dedicated just to audio files. But if I do that:

1 doesn't that drive get all fragmented really quickly with the creation and destruction of loads of temp files? I don't want any more fragmentation on that drive than I get already with the creation and deletion of various audio sessions.

2 doesn't that slow down the reading/playback of audio files if the drive head has to deal with temp files as well?

chebacca - make sense?
 
Very useful rant. And good question Dobro. If only I was smarter . . . Anyone know about this?
 
"1 doesn't that drive get all fragmented really quickly with the creation and destruction of loads of temp files? I don't want any more fragmentation on that drive than I get already with the creation and deletion of various audio sessions."

Depends. If the temp files are lots of little files--as you would find in, say, c:\windows\temp--then yes, you want to keep those temp files out of the way on the system drive. However, I THINK the temp files are more like audio files--large files, and not very many of them. This way when a temp file is created then deleted, it would leave a few huge chunks of contiguous free sectors, instead of lots of little sectors spread here and there over the whole drive.

You will still have some fragmentation with the temp files and the audio files, but it won't be nearly as severe. I think it's still important to defragment the drive every now and then.





"2 doesn't that slow down the reading/playback of audio files if the drive head has to deal with temp files as well?"

It would only effect performance if it was reading/writing the temp files at the same time as it was reading/writing the audio file. Again, that depends on the use of the Cool Edit temp files. If they're used for what I THINK they're used for (saving undo's) then this wouldn't really be an issue--unless you're running multiple, simultaneous sessions of Cool Edit, and playing back in one session while doing destructive edits/restores in the other sessions. But then you're just ASKING for trouble! :-)

But even IF Cool Edit DOES read temp files and audio files both during playback, I would say this would cause less of a problem than poorly fragmented files. In this case, the head would be bouncing between two places (that usually will not be far from each other). But a large, fragmented file could easily be written in many, many different places spread out across the whole drive.
 
dobro said:
chrisjob - yeah, I know synt recommends putting the first temp file on the largest drive. And my largest drive is the drive dedicated just to audio files. But if I do that:

1 doesn't that drive get all fragmented really quickly with the creation and destruction of loads of temp files? I don't want any more fragmentation on that drive than I get already with the creation and deletion of various audio sessions.

2 doesn't that slow down the reading/playback of audio files if the drive head has to deal with temp files as well?


Dude, don't ask me questions like this. How the heck am I supposed to know what to do. I don't even know what fragmentation is! :D


But seriously, I think if the temp files are going to clutter something, it's better your audio drive than your system drive. They're huge files, cause a new "track" is created everytime you change something in edit view, which I do alot. I'd think once the tracks are loaded in a .ses file, they're supported with RAM, and don't have to be calling on the audio drive every millisecond.


But, I really don't know. I defragment about every two weeks, and I've never had any problems with stutter or track count.


Cheers,
Chris
 
Back
Top