OpenPS3FTP v1.1 Arrives, an Open Source PS3 FTP Server App

No1 I never said I was trying to fill that gap in your pipe, you said it was down to slow hard drives.

So I am saying your wrong, and its getting boring now.were are you getting 25MB/s max from, thats slow as fooook and, and please don't tell me I am not getting 63MB/s, on my setup or tell me that, you can not get the speeds I'm saying when I have done this many a time. 63MB/s is 504Mbps, which is actually 1/2 the size to fit in that Pipe on my PS3 1000 base T network card.

Generally 60-70MB/s is what you get on Gbit normally , and I have done for a year or two now, since I had the kit to make the loads and so on.

Barry M8 it's you that don't get it!!!

no the sata connector on the end of your drive is capable of 3Gb/s thats not the actual throughput of the read write heads!, that's irrelevant when you look at the read write speeds of a mechanical drive. you're really not getting this are you, that hard drive will never fill a 3Gb/s pipe.

"Average read and write results of 74.5MB/sec and 48.1MB/sec place the 500GB Caviar Blue near the bottom of our benchmark table" -- Taken from pcpro.co.uk/reviews/hard-disks/252141/western-digital-caviar-blue-500gb

And those results aren't bad for a mechanical hard disc, the things were designed in the 80's and haven't really changed since. Your 63MB/s transfer speed might be right i'm not argueing i'm just saying it's nowhere near 100MB/s or the equivelent 800Mbit speeds you originally stated

I'm sorry Barry but I still don't understand your logic, you say "the hard drive is nowhere near capable of reading 3Gb/s". The spec of the drive, says it can. So the native transfer rate of 3.0 Gbit/s, with 8b/10b encoding buffered in 16megs of on board ram, will give the maximum uncoded transfer rate of 2.4 Gbit/s = 300 MB/s. The theoretical burst throughput of SATA 3.0 Gbit/s is roughly triple that of the ps3's 1 Gbit/s = 100 MB/s network card.

Don't forget Barry, the new 3.0 Gbit/s SATA devices we upgraded, in our PS3's are effectively the top end of the SATA drives now, or the bottom end of the new 6 Gbit/s drives = 600 MB/s Barry, wow thats fast. SATA also has NCQ that improves the performance.

So I really don't think the hard drive would ever come into the equation of FTP speeds, because it's 3 times as fast as the network card. I forgot one more thing,because I did this ages ago, was I created my own drives partition's and changed the starting sector, before installing win7, because it gives me 70MB/s , all day long. So my 63MB/s is true, because thats what I get.

ok first off your hard drive is nowhere near capable of reading 3Gb/s thats the theoretical max of sata, your hard drive doesn't actually read anywhere near that speed, try and remember the hard disk is the slowest part of a pc as it's the only real component containing moving parts (with the exception of SSD's btw).

second of all it doesn't matter what kind of drive you have in your PS3 you'll see no increase in speed as it's limited by the firmware (even with an SSD you'll see no speed increase).

As for your 63MB/s speed not only is it not "In some rear cases you can get 800 MBit /sec maybe the full 1000 MBit /sec" but you'll find its probably due to a mistake in the ftp apps calculation try transfer 1 640MB file (a dvdrip of a movie would do) and I guarantee it takes longer than 10-11 secs.

And stop calling me absolutely wrong all the time lol, I put both in my answer in Mb/s and MB/s (I included both hoping you'd see that even suggesting a 100MB/s transfer speed is ridiculous, what with most conventional hard disks being unable to write at that speed!)

Barry you're absolutely wrong, going on my last post, with the formula I used when I said 1000 MBit /sec,and 800Mbit/s. Sorry that was misleading and would be seen as incorrect, seeing people read in Megabytes and Gigabytes.

I do agree with you Barry about the drive maybe not being as fast as we would like it. but it is in no way slow running 3 Gb/s, so unlikely the drive could hinder the speed of the network transfer in anyway, unless it was seriously fragmented, or the drive needs replacing.

I’ll try to explain my reason for saying this Barry, so forgive me if I am being a complete ass and totally getting this all wrong, but I have to disagree with your logic on your post. I have a Western Digital Caviar Blue WD5000AAKS 500GB 7200 RPM 16MB Cache SATA 3.0Gb/s in my ps3.

So I have a drive with 16MB of cache capable of transferring 3 Gb/s across my 64bit powerpc bus, on a system thats only running a small simple Linux Kernel,a small ftp app,using its built in 1000 BASE-T full duplex network card, then connecting to my 3.6 quad core PC with like wise speed of drives, a 1000 BASE-T full duplex network card, but changing some of the PC card settings, and finally a extremely well made cat6 none crossed over cable, because you don't need it on a 1000 BASE-T cat6 link. And then tested with a penta scanner I own myself.

Anyway I was having to move a 30 gig movie back to my pc because I was formating the drive, before beta testing some homebrew, and knowing how long it could take, so I knew I'd have to change and set the connection settings to give me the full use of the 1000 BASE-T transfer speeds.

I set i,t to only have one ftp connection tho, because the way I thought was if you have more than one connection reading and writing at the same time, it slows things down with buffering, waiting. Regardless of how ever short the wait maybe, its still a bottle neck, I thought.

After letting it settle down and level out, with transferring that 30 gig file for about 90 seconds it settled at 63 MB/s
The formula I used. With both the network cards at both ends being Gigabit Ethernet set to frames at a rate of a gigabit per second,.

So 1 gigabit (Gbit/s, Gb/s, or Gbps ) = 1,000,000,000 bits per second.
Or a 1,000 megabits per second or
Or if you like bytes , it = 125,000,000 bytes per second.

So I said “In some rear cases you can get 800 megabits per second , that = 100 megabytes per second, and I have been getting 63 megabytes per second across my link.