Yeah, good points I mean 750000 bytes per second. In reality it's slower, around 450KB/s on average, but about 750KB/s burst speed.

I'm using a WPA2 connection to a cisco access point located less than 3 meters from my N900. What kind of connection are you using?

I don't have a speed report (not at home at the moment) but I'll post one when this evening and edit this post. For reference, I have a linksys WRT 54GS router running the latest Tomato firmware. The wifi setup is WPA2, pre-shared key, AES, "G only", Channel 2.

Edit: copying a large media file via sftp (source is Ubuntu 8.04 machine with default ssh and ip stack settings) resulted in a speed of around 1.8MBytes/second and very high cpu use (around 92%/600Mhz), though the cpu didn't seem to be the gating factor as it wasn't bouncing off of 100% (according to my manual observation via Conky, at least).

Copying a large media file via http using wget (same server, apache serving the file) resulted in an average speed of around 700kBytes/second. Cpu utilization was trivial, but the download speed was erratic..it would go anywhere from 300kBytes/second up to nearly a MegaByte/second. Tests done with the phone about 2 feet from the AP.

While not "blazing fast", the sftp speed seems ok.

Slightly OT, but I got similar performance over wifi using sshfs. I was pleased to say the least.

Watching with htop, the CPU usage between openssh during a sftp transfer or wget during a plain http/ftp is the same, neither is taxing the CPU much at all (around 15%).

I have a Linksys WRT610N running dd-wrt v24-sp2, bgn mixed mode, WPA2 with a pre-shared TKIP key, on Channel 13.

it's in the same room as the tablet.

Seems about the same setup as me then. I'm jealous

Other computers using same wifi in the same location get much, much faster speeds. So I dunno.

I'm doing mine on an open/cleartext network with ssh and a crappy motorola DSL/wifi modem.

Simply try moving your N900 to a different place. Like even 1 foot somewhere else or a different orientation can affect the signal significantly.

With my N800 (yes, 8), sometimes the transfer rate would get bad (~100kbytes/s) until I disconnected and reconnected, then it would go back to "normal" (~700kbytes/s). This was in almost the exact same spot. I have not yet had to play that trick on my N900, though.

You could also try putting some load on the CPU -- with my N800 (yes, 8 again) sometimes it seems that the transfer rate speeds up if the CPU is working. I think that the speed of the SD card transfers was related to the clock speed the CPU was currently running at. I haven't paid much attention to this on the N900 yet.

-jkq

You mean in the same way typing passwords and locks on doors waste time?

(the "conventional" way has it that b=bit, and B=8bits=byte)

stlpaul:
the only way to be sure is to carry out the test using other servers and other wifis.

As jebba said, try moving around. Because of the way TCP/IP is implemented, loss of packets because of bad signal will cause the connecting hosts to further reduce their speeds (to help with congestions, since it is assumed that the packets are lost due to congested networks). Therefore, even slight decreases in signal strength or minimal noise can have dramatic effects on wifi speeds.

I usually get about 1.5 MB - 2 MB, using ftp, scp, or samba or http (when close to the access point). The load doesn't kill my cpu (stays between 15% and 30%), but I do notice the device is a little sluggish.

If you can verify that your device is indeed under-performing, then you should have Nokia take a look at it.