[Prism54-devel] benchamark

[Luis R. Rodriguez]

OK I have better results now. After setting frameburst to a max of 5k, I
then set profile (DOT11_OID_PROFILES) to DOT11_PROFILE_TEST (4) and got
the following results:

wasp[~/prism54/prism54-cvs-latest]$ nttcp -T -t -l16384 moth-wlan-gw
     Bytes  Real s   CPU s Real-MBit/s  CPU-MBit/s   Calls  Real-C/s   CPU-C/s
l 33554432    8.90    0.42     30.1754    637.7109    2048    230.22    4865.3
1 33554432    8.90    3.39     30.1558     79.1845   13023   1462.99    3841.6

What goes on in TEST Profile? Beats me. Anyone else know the details of
what this does? 

Judging from my results, I'd guess you (Feyd) could probably reach results of up to 33 - 34Mbit/s.

	Luis

On Fri, Mar 05, 2004 at 02:18:27AM -0500, Luis R. Rodriguez wrote:
> On Thu, Mar 04, 2004 at 09:20:28AM +0100, Feyd wrote:
> > Hi,
> > 
> > I compiled the driver staticaly into the kernel to see if it affects performace
> > and the result is pleasant (I was getting about 10-12 Mbit with the driver as
> > module on those slow machines):
> > 
> > notes:~# nttcp -T -t -l16384 gw
> >      Bytes  Real s   CPU s Real-MBit/s  CPU-MBit/s   Calls  Real-C/s   CPU-C/s
> > l 33554432   11.17    0.31     24.0360    855.0180    2048    183.38    6523.3
> > 1 33554432   11.19    1.04     23.9794    257.1612   22540   2013.50   21593.3
> > 
> > after setting frameburst to 5000 (maximum allowed by windows driver) on both
> > machines (./setoid eth0 0x1b000008 136 19 0 0):
> > 
> > notes:~# nttcp -T -t -l16384 gw
> >      Bytes  Real s   CPU s Real-MBit/s  CPU-MBit/s   Calls  Real-C/s   CPU-C/s
> > l 33554432    8.58    0.51     31.3002    524.3689    2048    238.80    4000.6
> > 1 33554432    8.59    0.90     31.2364    298.6386   16113   1874.98   17926.0
> 
> These test are only performed with modules on systems running prism54
> cards. 
> 
> STA is PII 233Mhz / 56MB RAM
> AP is PMMX 200Mhz /  60MB RAM
> 
> ---------------------------------------------------------------------------------
> My results with frameburst set to default (0) is:
> 
> wasp[~/prism54/prism54-cvs-latest]$ nttcp -T -t -l16384 moth-wlan-gw
>      Bytes  Real s   CPU s Real-MBit/s  CPU-MBit/s   Calls  Real-C/s   CPU-C/s
> l 33554432   15.69    0.32     17.1102    844.2641    2048    130.54    6441.2
> 1 33554432   15.73    2.59     17.0688    103.6430   23171   1473.36    8946.3
> 
> ----------------------------------------------------------------------------------
> Now, setting frameburst to a max of 5000 on both STA an AP I get:
> wasp[~/prism54/prism54-cvs-latest]$ nttcp -T -t -l16384 moth-wlan-gw
>      Bytes  Real s   CPU s Real-MBit/s  CPU-MBit/s   Calls  Real-C/s   CPU-C/s
> l 33554432    9.53    0.41     28.1540    656.4209    2048    214.80    5008.1
> 1 33554432    9.55    3.36     28.1147     79.8915   13341   1397.28    3970.5
> -----------------------------------------------------------------------------------
> 
> Your list shows better results. I'd have to test building the driver
> into the kernel, I'm not sure how it'd help speed things.
> 
> One thing is for sure, maxing out the frameburst is *good*. :) 
> 
> -- 
> GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E



-- 
GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E