Social Feed

My rates were both through a wifi to my laptop and through a wired network to a desktop. Both gave approximately the same results. The wifi was not the Azbox wifi though, since it was an elete, it was hard wired to my wireless router then to the laptop.
I'll play with this a bit more tomorrow.

EDIT: Just did another quick test. I set up an FTP server on my desktop, and tested the speed between laptop and desktop. Came out to be about 28.5 Mbps.
Then I tested speed from Azbox to laptop, but transferred one of the OS files, ie a file off the memory module rather than the hard disk. Speed turned out to be 29 Mbps. So it does seem like the transfer from the USB hard drive is hurting the speed.
I wonder if the fellow (I forget who it was) who replaced the module with a hard drive has tested transfer rates between PC and Azbox? Or even someone with the Premium instead of Elete? Probably all my questions would be answered if I'd search the old messages. I think I'm re-inventing the wheel here, only mine is square.

B.J. said:

I wonder if the fellow who replaced the module with a hard drive has tested transfer rates between PC and Azbox?

Click to expand...

What module?

Is there any way to configure the external USB drive system (or any) settings via your AZBox UI?

B.J. said:

I'm curious.... for any of you who have an FTP program that gives you the bitrate while a file is transferring, what speed do you get when transferring a recording from an external USB drive? I know that other people have listed speeds calculated by other transfer methods, but I'm curious about the FTP speeds.

Reason I'm curious, is that yesterday, I made a couple 10 minute recordings on the AZBOX, and then transferred them to my computer. The 10 minute recordings took more than 15 minutes to transfer. This seemed odd, so I looked at the speed that the WSFTP program reported, and it was a bit more than 16 mbps, which seemed really slow. Since the recordings were 23mbps, it made me think that perhaps something was wrong with my external hard drive, although I guess that it worked OK getting that info TO the hard drive.
It's probably just some strange issue with the linux FTP server on the Azbox, or maybe it's some limitation in general for FTP transfers, and obviously, the Azbox won't use FTP when playing or streaming video, but I just wanted to insure that it wasn't some issue with the external drive I'm using.
thanks

Click to expand...

I'm getting about a 12 Mb file transfer using Gftp using sftp on Linux running on my 802.11g lappy. Not too bad for 11g.

B.J. said:

I'm curious.... for any of you who have an FTP program that gives you the bitrate while a file is transferring, what speed do you get when transferring a recording from an external USB drive? I know that other people have listed speeds calculated by other transfer methods, but I'm curious about the FTP speeds.

Reason I'm curious, is that yesterday, I made a couple 10 minute recordings on the AZBOX, and then transferred them to my computer. The 10 minute recordings took more than 15 minutes to transfer. This seemed odd, so I looked at the speed that the WSFTP program reported, and it was a bit more than 16 mbps, which seemed really slow. Since the recordings were 23mbps, it made me think that perhaps something was wrong with my external hard drive, although I guess that it worked OK getting that info TO the hard drive.
It's probably just some strange issue with the linux FTP server on the Azbox, or maybe it's some limitation in general for FTP transfers, and obviously, the Azbox won't use FTP when playing or streaming video, but I just wanted to insure that it wasn't some issue with the external drive I'm using.
thanks

Click to expand...

Most FTP client software that I've seen does not report transfer speed. FTP is generally faster than HTTP transfers, typically by 11% to 50% because it does not have the same overhead. FTP actually gains maximum transfer speed over time. The limiting factor in your case would probably be the physical layer of your LAN. Also, the AZBox is painfully slow due to limitations of processing speed and the small amount of available memory. The designers are asking this box to do a lot! The bottom line... If you have a lot of traffic going on your LAN and your transfer file size is small, expect it to take a while to upload to your computer. The main point here is that FTP inherently gains speed with larger file sizes.

knowmiddlename said:

Most FTP client software that I've seen does not report transfer speed. FTP is generally faster than HTTP transfers, typically by 11% to 50% because it does not have the same overhead. FTP actually gains maximum transfer speed over time. The limiting factor in your case would probably be the physical layer of your LAN. Also, the AZBox is painfully slow due to limitations of processing speed and the small amount of available memory. The designers are asking this box to do a lot! The bottom line... If you have a lot of traffic going on your LAN and your transfer file size is small, expect it to take a while to upload to your computer. The main point here is that FTP inherently gains speed with larger file sizes.

Click to expand...

Re FTP software, I was using WSFTP, which shows the rate during transfers, and also after the transfer says something like X bytes transferred in Y seconds. I also just used the old stopwatch method, which agreed.

The thing about FTP working better with larger file sizes, yeah, I guess that's probably true of most transfer methods, ie higher percentage going to data and less going to handshaking. Off topic a bit, but I have a weather web page, where every couple hours, I upload a bunch of gif files showing weather data from the weather station on top of my garage. The files are automatically uploaded by FTP. The funny thing is that before I "upgraded" to satellite internet, the files would transfer in about 1 minute over dialup. When I got satellite internet, the 1 minute transfer became over 8 minutes! I attribute that to extra handshaking, trying to set up the transfer with the inherent delays associated with satellite. I thought that there was a problem with respect to FTP and satellite internet, however when I did some tests comparing the transfer of many small files vs one big file, the satellite internet was 8 times faster with the big files.

I am surprised that you'd say FTP was faster than HTTP though, although perhaps there is more than one way to send data by HTTP. Reason I'm surprised, is that I could stream 40 mbps CBS HD (the old 4.2.0) through my LAN, but FTP seemed to max out at 29 mbps when I tried it yesterday. Although it just occurred to me that the 29 mbps transfer yesterday involved going through the 54 mbps wireless. I guess I should repeat that going between two of my desktop computers.

I also wonder if my specific LAN is overly complicated because several of the computers on the LAN have more than one NIC with different subnets, and the way I understand it, each time a packet is sent out, the computer has to decide which NIC to route the packets to. I keep meaning to eliminate the 2nd NIC, and put everything on the same subnet, but I have about 14 devices and my switch isn't big enough to put all the devices on one switch. I originally put all the video devices (TIVOs, ROKU, PopCornHour) on one subnet, and the regular LAN stuff on the other subnet. Anyway, it could be that my LAN is congested, but I think I demonstrated yesterday that the USB HD was responsible slowing down the transfers a lot.

You bring up a lot of interesting points. Data transfer is indeed a complicated process and one could definitely make a science project out of it. Yeah, you are right about all the variables like active FTP, passive FTP, network address translation/UDP handling, latency, the client software itself... the list seems endless... and now these newer and cheaper routers are equipped with stateful packet inspection to kill hammering (DOS) which can slow down transfers down even on the LAN side. Maybe a direct connection between the receiver and computer using a crossover cable would be a good starting point for troubleshooting.