Welcome, Guest. Please login or register.

Author Topic: Ariadne slooooow  (Read 2532 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline orangeTopic starter

  • Hero Member
  • *****
  • Join Date: Dec 2003
  • Posts: 2799
  • Country: 00
    • Show only replies by orange
Ariadne slooooow
« on: January 06, 2005, 07:43:22 AM »
I've just bought Ariadne card. :banana:

But its very slow  :-(
(using it on A4000 CSMKII '060, PIV, WB3.5 with Miami&smbfs)
I get only 13 Kbytes/sec when transferring Amiga->PC
even parallel cable would be faster..

and 150Kbytes/s PC->Amiga, which is very nice still not 10MBps, but good. IIRC, A1200 ('030) with 3COM PCMCIA had about 200Kbytes/sec.

I know there is no chance to get full 10MBps, but theres gotta be some way to get more, right?
What should I check first?

ariadne.device is v1.50
“Giving up is always an option, but not always a failure.”
 

Offline Castellen

Re: Ariadne slooooow
« Reply #1 on: January 06, 2005, 08:45:25 AM »
I have a similar setup with an Ariadne and get approx 200 kb/sec when doing transfers using SMBFS.

Using ariadne.device 1.44 with MiamiDX.

Have you tried using FTP instead to test the hardware and drivers properly?  FTP is faster as it doesn't have as many protocol overheads.

Also check you have the latest SMBFS, which is ver 1.63.

And also try SMBFS connecting to an Amiga running Samba, or a different PC.
 

Offline orangeTopic starter

  • Hero Member
  • *****
  • Join Date: Dec 2003
  • Posts: 2799
  • Country: 00
    • Show only replies by orange
Re: Ariadne slooooow
« Reply #2 on: January 06, 2005, 11:07:08 PM »
latest version is actually 1.66. I've switched to your 1.63 and now upload is ~70Kbytes/sec, great :banana:

thanks.. :-)
“Giving up is always an option, but not always a failure.”
 

Offline patrik

Re: Ariadne slooooow
« Reply #3 on: January 06, 2005, 11:53:01 PM »
@orange:

Try to get hold of AmiTCP/Genesis instead of Miami as it is a much faster TCP/IP stack.

Also when measuring speed you should remove as much protocol overhead as possible. A good tool for that is ttcp which measures the speed when sending/recieving raw tcp/udp packets. This will show you what speed the combination of your computer, network card and TCP/IP stack can manage without the added protocol overhead of for example ftp or samba. In other words it will give you a good estimate of how fast a TCP/IP-application can communicate at be as best on your system.

Amiga version of ttcp
Windows version of ttcp
Sourcecode for ttcp

---- Quick guide for how to use ttcp ----

- I will use amigaip instead of your Amigas ip-address and pcip instead of your pcs ip-address.

- I assume that you have installed ttcp in your path and that the executable for it is named 'ttcp'.

- You shall run ttcp from a shell/cli/command-prompt on both the Amiga and pc.

- I will call the shell/cli/command-prompt on both the Amiga and pc shell.

- I assume that your pc is fast enough to not have a negative impact on the results. A Pentium with a PCI network card should be fast enough.

Below I will describe what to input in the shell and the order of it on the Amiga and pc.

To test the speed when sending tcp-packets from your Amiga to your pc:
1. PC: 'ttcp -s -r'
2. Amiga 'ttcp -s -t pcip'

To test the speed when sending tcp-packets from your pc to your Amiga:
1. Amiga: 'ttcp -s -r'
2. PC: 'ttcp -s -t amigaip'

To test the speed when sending udp-packets from your Amiga to your pc:
1. PC: 'ttcp -u -s -r'
2. Amiga 'ttcp -u -s -t pcip'

To test the speed when sending udp-packets from your pc to your Amiga:
How to make this test is only included for reference. It will most likely not work as the protocol used - udp just sends packets as fast as possible without checking if it was recieved correctly. This in combination with the Amiga not being able to recieve packets as fast as the computer in the other end is sending them which usually is linespeed (100MBit in your case?) makes this test fail. Usually the Amiga doesnt even understand the test is done because it havent recieved all the packets sent by the pc and the pc reports speeds of over 10MByte/Sec.
1. Amiga: 'ttcp -u -s -r'
2. PC: 'ttcp -u -s -t amigaip'


/Patrik
 

Offline orangeTopic starter

  • Hero Member
  • *****
  • Join Date: Dec 2003
  • Posts: 2799
  • Country: 00
    • Show only replies by orange
Re: Ariadne slooooow
« Reply #4 on: January 11, 2005, 11:27:21 AM »
thanks,

here is what i got (copy/paste from PC DOS, Amiga shell is slightly different):

Amiga -> PC, TCP
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp
ttcp-r: socket
ttcp-r: accept from 10.1.92.197
ttcp-r: 16777216 bytes in 114.45 seconds = 143.15 KB/sec +++
ttcp-r: 3792 I/O calls, msec/call = 30.91, calls/sec = 33.13



PC -> Amiga, TCP
this for some reason didn't work:

D:\utils>ttcpw -s -t 10.1.92.197
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp  -> 10.1.92.197
ttcp-t: socket
ttcp-t: error=10061




Amiga -> PC, UDP

D:\utils>ttcpw -u -s -r
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001  udp
ttcp-r: socket
ttcp-r: 5447680 bytes in 11.20 seconds = 474.87 KB/sec +++
ttcp-r: 667 I/O calls, msec/call = 17.20, calls/sec = 59.54
ttcp-r:

Amiga side said 1400 Kb/s W-O-W  :-o



PC -> Amiga, UDP

ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001  udp  -> 10.1.92.197
ttcp-t: socket
ttcp-t: 16777216 bytes in 1.69 seconds = 9706.16 KB/sec +++
ttcp-t: 2054 I/O calls, msec/call = 0.84, calls/sec = 1216.82
ttcp-t:


Sorry if this sounds silly, but can that UDP thingy be used for transferring files since its a lot faster than tcp?
“Giving up is always an option, but not always a failure.”
 

Offline patrik

Re: Ariadne slooooow
« Reply #5 on: January 13, 2005, 11:04:50 AM »
@orange:

Comments on your results:
Amiga -> PC, TCP:
This result way to low considering your machine specs. I noticed that you are using the Miami TCP/IP stack which is very slow compared to AmiTCP/Genesis, but still it seems unreasonably slow. I will include results from my Amiga with 060 and Ariadne using AmiTCP/Genesis.

PC -> Amiga, TCP:
Make sure you always start the ttcp on the recieving end first - in this case on the Amiga.

Amiga -> PC, UDP:
This looks just about right using the Ariadne Sana2 device. You just cant seem to send UDP-packets faster for some wierd reason. You will also see that I didn't get any better results in this test on my system using AmiTCP/Genesis either. The wierd thing is that I get about double the speed when sending TCP packets instead which doesn't make too much sense as TCP packets requires more cpu. Also if I repeat this test with an A2065 (similar card, the same network chipset) I get the expected results - better when sending UDP packets than TCP packets, so it seems like it is connected with the Ariadne Sana2 device.

PC -> Amiga, UDP:
Now I am repeating myself from the end of the last post quite some, but anyhow.. This result will just show how fast your pc can send packets to the buffers in your switch. This as when sending packets with the UDP protocol, they are just sent as fast as possible without checking if they were recieved correctly. This in combination with the Amiga not being able to recieve packets as fast as the computer in the other end is sending them which usually is linespeed (100MBit in your case?) makes this test fail. Usually the Amiga doesnt even understand the test is done because it havent recieved all the packets sent by the pc and the pc reports speeds of around 10MByte/Sec (if you have a 100Mbit switch).

My results:
Hardware:
A4000
Ariadne
CyberStormPPC 060@50MHz
Buster 11

Software:
AmiTCP Genesis 4.6
ariadne.device 1.50
Kickstart 3.1
Workbench 3.9

Amiga -> PC (TCP):
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp  -> 192.168.0.1
ttcp-t: socket
ttcp-t: connect
ttcp-t: 16777216 bytes in 18.66 real seconds = 877.81 KB/sec +++
ttcp-t: 2048 I/O calls, msec/call = 9.33, calls/sec = 109.73
ttcp-t: 0:18real

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 18.06 real seconds = 907.34 KB/sec +++
ttcp-r: 4222 I/O calls, msec/call = 4.38, calls/sec = 233.81
ttcp-r: 0:18real

Amiga -> PC (UDP):
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001  udp  -> 192.168.0.1
ttcp-t: socket
ttcp-t: 16777216 bytes in 40.97 real seconds = 399.87 KB/sec +++
ttcp-t: 3077 I/O calls, msec/call = 13.64, calls/sec = 75.10
ttcp-t: 0:40real


/Patrik
 

Offline Varthall

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 633
    • Show only replies by Varthall
Re: Ariadne slooooow
« Reply #6 on: January 13, 2005, 11:51:12 AM »
Quote

orange wrote:
Sorry if this sounds silly, but can that UDP thingy be used for transferring files since its a lot faster than tcp?


UDP doesn't check if the packets were received correctly, this is why it is faster. You would risk to lose data if you'd send files with this protocol.

Varthall
AmigaOne XE - AmigaOS 4.1 - Freescale 7457 1GHz - 1GB ram
MPlayer for OS4: https://sourceforge.net/projects/mplayer-amigaos/
 

Offline orangeTopic starter

  • Hero Member
  • *****
  • Join Date: Dec 2003
  • Posts: 2799
  • Country: 00
    • Show only replies by orange
Re: Ariadne slooooow
« Reply #7 on: January 13, 2005, 01:55:48 PM »
I got results from PC->Amiga, the problem was that MiamiDX FIREWALL was ON! (and I forgot to check it, duh)
Here are the results:

D:\utils>ttcpw -s -t 10.1.92.197
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp  -> 10.1.92.197
ttcp-t: socket
ttcp-t: connect
ttcp-t: 16777216 bytes in 31.67 seconds = 517.30 KB/sec +++
ttcp-t: 2048 I/O calls, msec/call = 15.84, calls/sec = 64.66
ttcp-t:

It seems to affect Amiga2PC speed, too!!!! :-o  :-o
I got now  (Amiga->PC) WITHOUT FIREWALL:
D:\utils>ttcpw -s -r
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp
ttcp-r: socket
ttcp-r: accept from 10.1.92.197
ttcp-r: 16777216 bytes in 28.97 seconds = 565.57 KB/sec +++
ttcp-r: 3870 I/O calls, msec/call = 7.67, calls/sec = 133.59
ttcp-r:

smbfs gives me ~220 Kbytes/sec woow

yessss "..speed, gimme what i need.."
 :hat:


BTW, I've turned off SOCKS,  maybe that was important too.
“Giving up is always an option, but not always a failure.”
 

Offline patrik

Re: Ariadne slooooow
« Reply #8 on: January 13, 2005, 04:17:02 PM »
@orange:

Great news! :) Very reasonable too as firewalling adds a lot of overhead.

If you want even more speed - get hold of AmiTCP/Genesis.


/Patrik
 

Offline fx

  • Sr. Member
  • ****
  • Join Date: Mar 2002
  • Posts: 347
  • Country: se
  • Gender: Male
    • Show only replies by fx
    • UHC Tools
Re: Ariadne slooooow
« Reply #9 on: January 13, 2005, 10:45:33 PM »
Dump Miami and go for AmiTCP or Genesis instead! They're much faster than Miami!
Slightly bored and severly confused..