A1200 overclocked & 2Mbit broadband

[patrik]

@Gerbinist:

The A1200 with 060 and a PCMCIA-network card can actually shove data over the network pretty fast. These are the results from my A1200:

Hardware:
A1200
Blizzard1260 060@50MHz
CNet CN40BC network card

Software:
AmiTCP 4.3
cnet.device 1.8b
Kickstart 3.1
Workbench 3.1

Non-default settings:
Kickstart in FastRAM
exec.library in FastRAM

Amiga -> PC (TCP):
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp  ->
ttcp-t: socket
ttcp-t: connect
ttcp-t: 16777216 bytes in 24.28 real seconds = 674.89 KB/sec +++
ttcp-t: 2048 I/O calls, msec/call = 12.14, calls/sec = 84.36
ttcp-t: 0:24real

Amiga -> PC (UDP):
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001  udp  ->
ttcp-t: socket
ttcp-t: 16777216 bytes in 27.36 real seconds = 598.79 KB/sec +++
ttcp-t: 2737 I/O calls, msec/call = 10.24, calls/sec = 100.03
ttcp-t: 0:27real

PC -> Amiga (TCP):
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp
ttcp-r: socket
ttcp-r: accept from 192.168.0.1
ttcp-r: 16777216 bytes in 17.08 real seconds = 959.36 KB/sec +++
ttcp-r: 5818 I/O calls, msec/call = 3.01, calls/sec = 340.67
ttcp-r: 0:17real

Some general tips to get good performance in order of importance are:
- Use the AmiTCP/Genesis TCP/IP stack
- Relocate exec.library to fastmem
- Relocate the kickstart to fastmem


/Patrik

[patrik]

@Gerbinist:

Ofcourse, if you use the incoming data in a very cpu intensive way, you will have a rather low max. Say if you would be streaming a mpeg4 stream, you would not need many tens of kilobytes of data per second before the 68060 would be saturated performance wise. Though, if you intend to use your Amiga for something that is more intensive network wise rather than cpu wise, these figures represent a rough upper level a well written and effective application can achieve.


/Patrik

[patrik]

@Gerbinist:

Ttcp is just a tool to measure the raw TCP/UDP performance you can achieve between two systems. The numbers you get represent how fast data can be transferred between your computers memory and another computers memory using either TCP or UDP packets. In say a simple application that downloads files to your harddrive using the HTTP protocol - a HTTPGet application, the application will also have to deal with the HTTP protocol plus write the data to a file on your harddrive.

The above example with a HTTPGet application would benefit from SCSI as it usually has a higher transfer rate plus often uses DMA so there is more processing power left for the TCP/IP stack and the application itself.

For networking performance in general on the Amiga, the TCP/IP stacks are a very big bottleneck. Neither AmiTCP/Genesis or Miami are very effective to say the least. Though AmiTCP/Genesis is much faster than Miami.

Especially if you have a fast connection - slow, non DMA harddrive controllers (A1200/A4000/A600 stock IDE for example) imposes a big bottleneck as just writing the file to disk will require a huge chunk of the available cpu time.


/Patrik