Genesis/AmiTPC slower than MiamiDX. What am i doing wrong?

[AmigaMance]

Hi. Everyone says that Genesis is faster than MiamiDX, both in CPU usage and transfer rates, but i'm not experiencing this and i wonder why!
 My connection is a 2Mbps ADSL one and i'm using a router which is connected to my Amiga 1200 through a PCMCIA network card, driven by cnet16.device.
 In MiamiDX, my download rate reaches the maximum speed, which is about 216 kbps, easily. In Genesis, it tops at about 196 kbps. CPU usage is the same with both stacks. I have tried to tweak the settings of Genesis/AmiTCP many times, without seeing much improvement. Here are the settings that i'm currently using:


AmiTCP.config:

PRIORITY = 1

MBUF_CONF Initial =        2
MBUF_CONF Chunk =         64
MBUF_CONF ClChunk =        4
MBUF_CONF MaxMem =      4096
MBUF_CONF ClusterSize = 1500

;LOG Count =     4
;LOG Len =     128
;LOG Filter =    7
LOG FilterCons = 4
LOG FilterFile = 4

DebugSana = NO
DebugICMP = NO
DebugIP =   NO
Gateway =   NO
IPSendRedirects = YES

TCP_SendSpace = 32768
TCP_RecvSpace = 32768

ConsoleName = "t:AmiTCP.txt"
LogFileName = "t:AmiTCP.log"

[JC]

Well, back when I was online using miami and dialup, miami was much faster than anything else I tried, as a matter of fact I had a friend who said it was faster than his peecee hooked to a cable modem.

[Zac67]

You might want to raise TCP_RecvSpace to its maximum of 64240 to make up for high latency connections. 32768 should be enough to saturate a 2 Mbps line with a round trip delay of up to 100 ms though.
Since the uplink is much slower on ADSL, raising the TCP_SendSpace wouldn't make too much sense - but doesn't hurt much either, apart from memory consumption.

BTW: Does anyone know if Genesis / Miami are able to use the window scaling option from RFC 1323?

Wikipedia: TCP tuning

[AmigaMance]

@JC
 Yeah, i remember that miami performed slightly faster for me, even with a dial-up connection.

@Zac67
That's the TCP_RecvSpace value i have set in MiamiDX too. You are right that 32kb's are enough for my connection. Bigger values doesn't help..

[kolla]

I never experienced AmiTCP faster than MiamiDx, and always regarded that claim as propaganda by people with some whack agenda.

[Matt_H]

Is it possible that the same bug that this thing fixes is also zapping your overall transfer speed?

[Piru]

I never experienced AmiTCP faster than MiamiDx, and always regarded that claim as propaganda by people with some whack agenda.

I've always found AmiTCP/IP faster than MiamiDX in real performance tests (say for example moving a large file via FTP in a LAN).

[Daedalus]

I've also found AmiTCP to be faster and comsume less CPU time during transfers on lower-specced machines - I switched to it on my 030 A1200 and it's so much faster!

[Framiga]

my AmiTCP.config is:

PRIORITY = 5

MBUF_CONF Initial =     2
MBUF_CONF Chunk =       64
MBUF_CONF ClChunk =     4
MBUF_CONF MaxMem =      2048
MBUF_CONF ClusterSize = 2048

;LOG Count =     4
;LOG Len =     128
;LOG Filter =    7
LOG FilterCons = 7
LOG FilterFile = 7

DebugSana = no
DebugIP =   no
Gateway =   no
IPSendRedirects = no
;UseNameServer = SECOND
;UseLoopBack = YES

TCP_SendSpace = 32768
TCP_RecvSpace = 32768

[pVC]

Here's some tests I made with my systems with different stacks... It seems that you can't see that much difference when downloading with IBrowse, but for FTP the difference is clear.

Code: [Select]


Stack       FTP download   FTP upload   HTTP download
-----------------------------------------------------
A1200/030@50 (Lucent Tech WaveLAN Silver)
Genesis         420 kB/s     390 kB/s        190 kB/s
MiamiDX         220 kB/s     160 kB/s        160 kB/s

A1200/060@60 (Realtek 8139)
Genesis        1420 kB/s    1015 kB/s        500 kB/s
MiamiDX         640 kB/s     330 kB/s        455 kB/s
Miami3.x        630 kB/s     340 kB/s        400 kB/s

Pegasos 1 G3@600 (On-board VIA Rhine)
NetStack       6950 kB/s    6350 kB/s       1250 kB/s
Genesis        6850 kB/s    5910 kB/s       1250 kB/s
MiamiDX        3500 kB/s    2250 kB/s       1250 kB/s


FTP transfers were made in 10/100 Mbps LAN with 25 MB and 100 MB files. Results were pretty stable.

HTTP download was made with 10 Mbps VDSL with IBrowse. ISP's proxy was used, but results may still have bit variation. On 060 HTTP transfers were varying pretty much, those are the max values and that makes them less reliable.

[AmigaMance]

Hello.
 I finally found some time to look at the issue again.
Thank you for all of your suggestions!

@Matt_H
 I have already applied that patch.

@framiga
 There was no improvement with your settings.

@pVC
 Mine is still slower, even with FTP servers.


 Anyway.. I like Miami. The only problem with it, is that it can't handle excessive internet traffic. It corrupts the downloaded data. This happens, for example, when you try to download from a torrent that has many seeders. It is a known bug.

[NovaCoder]

I'm also finding transfer speed is a bit slow on my setup.  I'm using AmiTCP via EasyNet so I might try having a look at my AmiTCP.config....anyone got any suggestions?

Do I also need to install that patch?  I seem to remember having trouble accessing SSL sites with iBrowse.

[save2600]

I'm also finding transfer speed is a bit slow on my setup.  I'm using AmiTCP via EasyNet so I might try having a look at my AmiTCP.config....anyone got any suggestions?

Do I also need to install that patch?  I seem to remember having trouble accessing SSL sites with iBrowse.

Funny, for the past 10 years, I've never been able to get Genesis to run on *ANY* of my
Amiga's. Dial up or broadband. With a cable modem hooked, Config program currently
won't get past that initial boot request.  :-(   Termite TCP on the other hand worked
great back in the day though. lol

But regarding SSL sites and Miami... you have to download and install the AmiSSL plug-in
script and encryptions. I believe I got mine from Aminet. There are a couple of different
versions, so make sure you're downloading the correct one for your setup. SSL works
great with iBrowse.