Ok, that's more reasonable that way, though still a bit slow on your side, compared to the PC.

But it's also known amitcp isn't exactly optimally suited for inet speed, these days. With a local test, you'd still probably reach 8MB/s or so, though (with a plain HTTP/FTP transfer).
To be noted OWB would need some "setenv OWB_POLLTIME 1" to get optimal speed there (otherwise it won't go higher than 1.5MB/s with the default value of 10ms (webkit default)).
I also read removing "DEBUG" argument from netstack could help, but i haven't verified it yet. Increasing TCP send/recv window could also help a bit.

Regarding Youtube, i don't share the same experience as you. When youtube acts slow, it acts slow on any machine/software here (be it on windows/linux/morphos or wget/tubexx/owb/firefox/...). And it can act slow as hell (2kB/s) and fast again (>300kB/s) the minute after, too.
Also, your test on the PC implies you ask Youtube to serve a particular format (flv), which may very well be prioritized over the ones served for HTML5 (mp4). But i really hope it's not happening that way. :)

I set the OWB_POLLTIME to 1 and removed the DEBUG from the netstack.
Then rebooted (first time in 3 days so I guess my ram was pretty fragmented)
Now OWB and Ibrowse gets about 4000 Kbps !

Thanks!

@Fab

OT: You don't happen to play StarCraft II by any chance?

I just killed someone named FAB in an online game there...

@takemehomegrandma

Nope, i don't have any powerful enough machine to play it. :)
But i used to play starcraft quite a lot at university between lessons. :)