Why does it take 50 seconds to open a 260 megabyte file? Only 5 megs a seconds

[blstriker]

I just got a Maxtor 45 gig ata100 7200 with a Maxtor ultra 100 controller (made by Promise - same as ultra 100). I'm running windows 2000 pro and when I use sound forge XP 4.0 to open a 260 meg wav audio file, it takes 50 seconds or about 5 megs per second.

Isn't 5 megs per second pretty slow in this case? I thought it should be able to really fly, but this isn't the case.

I'm using Maxtor's drivers for the controller card which are the same as promise's current drivers.

The 45 gig is in one huge partition - i hate partitioning.

Any ideas?

Thanks..

 

[jinsonxu]

How much ram? How fast is your rig?

 

[deadlock]

Probably not much ram or cpu too slow. You sure your board handles ATA/100 and you got the proper cables in? Your partition size doesn't matter in this case unless your drive is badly fragmented, though under Win2000 the FAT is very efficient with minimal space wastage.

Try copying the file to another location on your hdd. If it takes just as long, then it's probably one of the above. If it copies very fast, then it's AudioForge.

Deadlock

 

[Mytv]

Hard drives are the slowest part on any system even with 100ata. Given the file is so large the hdd has to access from different locations of the hdd meaning the access time is slowed.

Media and audio files are the slowest when it comes to copying files.

Do you have dma checked in windows properties correctly?
Run Hdtach to find your harddrive's potential for tweaks.

http://www.tcdlabs.com/hdtach.htm
If you get 30 megs plus your doing good.

 

[blstriker]

Sorry, forgot the specs:

Tyan Tiger 100
256 pc100
Dual 366@550

only 4 gigs of 45 used.

I'll try the hdtach..

 

[BurnItDwn]

Id think it to be the ram for sure


try opening like a 100MB wav file ... it should go much faster ...

 

[Hardware]

Takes 5s for me

 

[Mday]

yah, try a smaller file, or more RAM.

 

[Hardware]

get a dtla raid 60meg/s

 

[Chuffmaster2k]

Defrag is another possibility. Good Luck.

 

[Adul]

Since the file is obviously larger than the amount of system RAM you have available, your OS is forced to go to the swap file to make up for it. So in your case, it is the additional swapping that is slowing the opening of your file.

 

[Pauli]

Also, you need to take into account that SoundForge is processing the file that you're reading. It may be doing some complex manipulation to get the stored file into its process. This is not a good measure of hard disk throughput.

 

[Topochicho]

you need at least 512MB to edit a 260MB sound file with any real speed. It'll take at least 384 to load the file into forge on 2000.