RT to HOST transfer rate problem in cRIO-9073 ?

Dear Sir,
Since past 2 months I am facing a problem in data transfer in cRIO 9073.
I'm using two c series modules for data acquisition. NI 9205 for analog input and NI 9421 for digital input. Where Max sample rate of 9205 is 250kS/s.
All seems perfect from FPGA to RT data transfer using FIFO. I m able to read instant value in RT when I change given input. In FPGA I m successfully reading and transferring 32 samples per 200us. In RT I m reading 16000 samles from FIFO and push it into shared variable. (No time out occurs in FIFO) therefore all I can say I m acquiring perfectly till RT.
But when I tries to transfer dta from RT to HOST, at the time I m facing a problem. Host is updating 3-4 seconds late than RT. I have tried shared variable, TCP & Network steaming & faced same problem in all the cases.
I m not able to get that where the problem is? Because I can see instant change as per input in RT. dont know what happened between RT to Host data transferring.
Please do let me know what can be the possible reasons. Crossover Ethernet port or cable or chassis data transfer rate what can be the cause?????
Regards,
Pranav Parik
Application Engineer
Alliance Partner of National Instruments
Attachments:
RT.jpg ‏328 KB
RT1.jpg ‏171 KB

What is the priority of the VI you're running? I'd be concerned that maybe you've starved out the ethernet transmit thread or something.
-Danny

Similar Messages

Usb transfer rate problem with bootcamp

hello
drivers for uEye cameras are only available for windows platforms. so i am running windows xp on the latest mac mini with the latest bootcamp drivers in order to use the camera.
everything works great until i plug in another usb device. the transfer rate of the camera decreases dramatic (1/2). the second usb device is an usb hub with a microcontroller. it consumes only low transfer rates.
this constellation works perfect on other pcs. i can't compare it on os x because no drivers for the camera are available.
are there known issues with usb transfer rates on intel mac minis? firewire cameras and harddrives should suffer similar problems.
greetings
michael

are there known issues with usb transfer rates on
intel mac minis? firewire cameras and harddrives
should suffer similar problems.
Welcome to Apple Discussions!
To address this specific point - no, there are no known issues with USB transfer rates that are common to Macs but not PCs. The weakness of the USB standard is that it is controlled by the host system rather than a dedicated controller, thus transfer rates (on both Mac and PC platforms) are determined by what the system is doing overall. As a result, transfer rates vary quite dramatically. Firewire, on the other hand, has a dedicated controller which ensures that a consistent data rate is achieved, almost regardless of other system activity. That's why you will often see it recommended that FW is used for external drives rather than USB, since while USB will generally provide better burst rates of data transfer, FW will generally provide far better sustained data rates, despite being theoretically slower.
In your situation, I can't help but wonder if the hub you mention is not causing the system some issues. It would not have to be a matter of it causing any significant data transfer itself, but could be the result of the hub's controller forcing the system into activity which then suppresses potential performance from the camera.
One thing is sure: if the camera works well without the hub connected, but degrades in performance with it, the issue is not with the system or the camera, but the hub.

K7 Pro AGP Transfer Rate Problem

I have noticed that despite this board claiming to support AGP 1x AND 2x rates, I can only get 1x out of it.
Sideband addressing is also supposedly supported but disabled. :O
I have altered these settings to AGP2x and sideband enabled using GF Tweak utility but this resulted in crashes, (when both or either individual setting was altered). X( Powerstrip just won't make the changes.
Is this a mobo/vid.card problem?
A tech told me the other day that it could be OS related?
PLEASE help me optimise my machine's gaming performance...
My system is
Athlon 700/MSI 6195 K7 Pro v1.0b (AMIBIOS v1.3)
512MB PC133 SDRAM (AGP Aperture: 128MB)
ASUS GF2MX400 64MB (planning to move to GF4MX460)
Creative SB Live! Value
WD 20GB HDD 7200RPM
Win98SE

Well, after trawling through about 1000 posts in the old forum here and also MSI forum @ amdmb.com, I have come to the following (depressing) conclusions:
The AMD-751 Irongate Northbridge chipset has well-known stability problem with AGP2x rate and therefore will have to stay stay at 1x AGP transfers. ;(
I tried the main suggestions:
1. Update AMD chipset drivers from AMD's website (v1.30 = final release containing AGP driver v4.80)
2. Use Geforce Tweak Utility or NVMax4 (both software for editing registry) to override registry settings to enable Irongate AGP2x & Sideband memory addressing. This just caused system crashes.
Powerstrip is another vid tweaker but works differently to the other two and just will not make changes that aren't supported.
Although Sideband memory addressing (for boosting data rates and performance) is supported by MS-6195 m/b, it has been deliberately disabled by ASUS in their V7100Pro (GF2MX400 64MB) BIOS, as it is a performance gain with serious stability risks (other MFRs also have done this deliberately on certain cards). So even though mobo & vid card hardware "suppport" SBA, no amount of regediting (GTU or NVMax4) was gonna get anything more than a lockup out of that "feature". There is a beta BIOS around at an ASUS download website, which may have sideband enabled, but "enter at your own risk"...
I also note that MS-6195 is AGP rev1.0 whereas most current vid cards are AGPrev2.0 - this appears to be a voltage difference issue with minor significance (?) I guess as I noted plenty of succesful use of GF3Ti cards with K7 Pro mobo's, so a hopefully a "tarted-up" NV17 (GF2Ti) chip in the GF4MX series should be OK...
So my next move is to just try a cheap Eagle GF4MX460 card as a stop-gap upgrade until the 333FSB Athlon's arrive in OZ and then it'll be "Adios" to the whole PC...

How to achieve the maximum file transfer rate from PXI to local host?

I will have to copy a huge amount of data (as big as 50 GB) from a PXI-8106 unit on site to a laptop. Currently it would take several hours. It is critical to max out the data transfer rate.
The standard method we've been using is just drag and drop using Windows Explorer via FTP. I tried to use FTP VIs with Filezilla Server as well but the transfer rate is only like 1.5 MB/s. Is this normal? Once I saw it was 3.0 MB/s but for some reason, that isn't happening now.
For another option, I tried to transfer data to a USB flash drive but it's even slower. As far as I know, USB 2.0 transfer rate is supposed to be around 60 MB/s but why would it be slower than 1.5 MB/s? What could be the speed limiting factor in my file transfer setup?
Any tips on improving file transfer rate would be appreciated!

Sustained 40 MB/s? That is my dream speed! The maximum speed I've ever seen here was about 25 MB/s, which is still very good, and that happened only after copying back and forth, which I explained above. Let me go through what I did with screencaps first.
These are the test tdms files to transfer in the PXI: an original file witten in the PXI and its copy file. I copied the original file from PXI to laptop and renamed it (added '_copy') and then copied it back to PXI.
FTP module is transferring the original file to the Filezilla server on laptop. Note the low speed.
FTP module is transferring the copy file to the Filezilla server on laptop. Note the higher speed.
This is the FTP sub VI I'm using. It transfers files in sub-folders (one level lower), too. The data connection is set to 'passive' on the FTP Put Multiple Files VI but it doesn't seem to make any difference. I attach the sub VI.
You tried the file transfer with a 500 MB text file. Would there be any difference if the file type was tdms? Would the RAM size matter? It is 2GB here.
And the LED is orange, which means Gigabit.
Another question: Is there any way to programmatically stop file transfer in progress? Currently, I just have to restart the PXI.
Thank you!
Attachments:
FTP.vi ‏40 KB

Transfer Rate Upload/Download

Dear Freindzs,
I am looking a solution / answer for a querry related to FTP upload & download. However this querry is not directly related to Cisco, But reason for raising this problem in this forum is that i have searched a lot but did'nt find any convincing reply. If anyone of you can spend some time on this to reply. please...
1) We are a ISP at India. We are getting querry related to USA sites/FTP (Download & Upload) from our customers since couple of time.
Problem :- Customers/We are not getting upload / download transfer rate more then 1.8 - 2Mbps even on high bandwidth at our customer backend. i.e DS3 or STM-1. in short in all cases/bandwidth the upload & download for USA sites/FTP are not reaching beyond 2 Mbps.
We have checked all our peering / routing all fine and infact tryed different-different combinations/routing but the response from abroad sites are still not more then 2 Mbps even with best possible combinations.
2) For Eg:- a customer having 4 Mbps(1:1) internet link from us. Hence the standard transfer rate should be 512KB/s(or close to this) while upload & download. But while downloading or upload to FTP servers. sometime we are getting Channelised response (transfer rate) in multiple sessions. i.e 256KB/s in one and 256KB/s in other, so total 512KB/s. question is what are the all possible reasons that why we are not getting the full or even close to full transfer rate in single session (512KB/s).
3) What are the factors which impacting the download / upload response except routing. How we can get know or investigate that particular FTP server having bandwidth contraints or having policy configured to limit the upload/download session..
4) If anyone have some good documents on FTP/ Upload or Download working with key points...kindly share

Dear Freindzs,I
am looking a solution / answer for a querry related to FTP upload &
download. However this querry is not directly related to Cisco, But
reason for raising this problem in this forum is that i have searched a
lot but did'nt find any convincing reply. If anyone of you can spend
some time on this to reply. please...1)
We are a ISP at India. We are getting querry related to USA sites/FTP
(Download & Upload) from our customers since couple of time.Problem
:- Customers/We are not getting upload / download transfer rate more
then 1.8 - 2Mbps even on high bandwidth at our customer backend. i.e
DS3 or STM-1. in short in all cases/bandwidth the upload & download
for USA sites/FTP are not reaching beyond 2 Mbps.We
have checked all our peering / routing all fine and infact tryed
different-different combinations/routing but the response from abroad
sites are still not more then 2 Mbps even with best possible
combinations.2)
For Eg:- a customer having 4 Mbps(1:1) internet link from us. Hence the
standard transfer rate should be 512KB/s(or close to this) while upload
& download. But while downloading or upload to FTP servers.
sometime we are getting Channelised response (transfer rate) in
multiple sessions. i.e 256KB/s in one and 256KB/s in other, so total
512KB/s. question is what are the all possible reasons that why we are
not getting the full or even close to full transfer rate in single
session (512KB/s). 3)
What are the factors which impacting the download / upload response
except routing. How we can get know or investigate that particular FTP
server having bandwidth contraints or having policy configured to limit
the upload/download session..4) If anyone have some good documents on FTP/ Upload or Download working with key points...kindly share****
Hi,
The answer depends on the operating systems on the hosts not on the routers check out the below link to detailed procedures on different o.s. :
http://www.psc.edu/networking/projects/tcptune/
for example
http://www.psc.edu/networking/projects/tcptune/#WindowsXP
for Win XP
Hope to help
Ganesh.H

How to find the max data transfer rate(disk speed) supported by mobo?

I plan on replacing my current HDD with a new and bigger HDD.
For this I need to know the max data transfer rate(disk speed) that my mobo will support. However, dmidecode is not telling me that. Am I missing something?
Here's dmidecode:
# dmidecode 2.11
SMBIOS 2.5 present.
80 structures occupying 2858 bytes.
Table at 0x000F0450.
Handle 0xDA00, DMI type 218, 101 bytes
OEM-specific Type
Header and Data:
DA 65 00 DA B2 00 17 4B 0E 38 00 00 80 00 80 01
00 02 80 02 80 01 00 00 A0 00 A0 01 00 58 00 58
00 01 00 59 00 59 00 01 00 75 01 75 01 01 00 76
01 76 01 01 00 05 80 05 80 01 00 D1 01 19 00 01
00 15 02 19 00 02 00 1B 00 19 00 03 00 19 00 19
00 00 00 4A 02 4A 02 01 00 0C 80 0C 80 01 00 FF
FF 00 00 00 00
Handle 0xDA01, DMI type 218, 35 bytes
OEM-specific Type
Header and Data:
DA 23 01 DA B2 00 17 4B 0E 38 00 10 F5 10 F5 00
00 11 F5 11 F5 00 00 12 F5 12 F5 00 00 FF FF 00
00 00 00
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A17
Release Date: 04/06/2010
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 4096 kB
Characteristics:
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
EDD is supported
Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
BIOS Revision: 17.0
Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: OptiPlex 755
Version: Not Specified
UUID: 44454C4C-5900-1050-8033-C4C04F434731
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified
Handle 0x0200, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Dell Inc.
Product Name: 0PU052
Version:
Handle 0x0300, DMI type 3, 13 bytes
Chassis Information
Manufacturer: Dell Inc.
Type: Space-saving
Lock: Not Present
Version: Not Specified
Asset Tag:
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
Handle 0x0400, DMI type 4, 40 bytes
Processor Information
Socket Designation: CPU
Type: Central Processor
Family: Xeon
Manufacturer: Intel
ID: 76 06 01 00 FF FB EB BF
Signature: Type 0, Family 6, Model 23, Stepping 6
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Not Specified
Voltage: 0.0 V
External Clock: 1333 MHz
Max Speed: 5200 MHz
Current Speed: 2666 MHz
Status: Populated, Enabled
Upgrade: Socket LGA775
L1 Cache Handle: 0x0700
L2 Cache Handle: 0x0701
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 2
Core Enabled: 2
Thread Count: 2
Characteristics:
64-bit capable
Handle 0x0700, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 32 kB
Maximum Size: 32 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: None
System Type: Data
Associativity: 8-way Set-associative
Handle 0x0701, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 6144 kB
Maximum Size: 6144 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: <OUT OF SPEC>
Handle 0x0800, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: PARALLEL
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-25 female
Port Type: Parallel Port PS/2
Handle 0x0801, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SERIAL1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x0802, DMI type 126, 9 bytes
Inactive
Handle 0x0803, DMI type 126, 9 bytes
Inactive
Handle 0x0804, DMI type 126, 9 bytes
Inactive
Handle 0x0805, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0806, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB2
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0807, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB3
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0808, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB4
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0809, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB5
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB6
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB7
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB8
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: ENET
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: RJ-45
Port Type: Network Port
Handle 0x080E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MIC
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x080F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0810, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-IN
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0811, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: HP-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0812, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MONITOR
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x090A, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT1
Type: x1 Proprietary
Current Usage: In Use
Length: Long
Characteristics:
PME signal is supported
Handle 0x0901, DMI type 126, 13 bytes
Inactive
Handle 0x0902, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT2
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 2
Characteristics:
5.0 V is provided
3.3 V is provided
PME signal is supported
Handle 0x0903, DMI type 126, 13 bytes
Inactive
Handle 0x0904, DMI type 126, 13 bytes
Inactive
Handle 0x0905, DMI type 126, 13 bytes
Inactive
Handle 0x0906, DMI type 126, 13 bytes
Inactive
Handle 0x0907, DMI type 126, 13 bytes
Inactive
Handle 0x0908, DMI type 126, 13 bytes
Inactive
Handle 0x0A00, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Disabled
Description: Intel Graphics Media Accelerator 950
Handle 0x0A02, DMI type 10, 6 bytes
On Board Device Information
Type: Ethernet
Status: Enabled
Description: Intel Gigabit Ethernet Controller
Handle 0x0A03, DMI type 10, 6 bytes
On Board Device Information
Type: Sound
Status: Enabled
Description: Intel(R) High Definition Audio Controller
Handle 0x0B00, DMI type 11, 5 bytes
OEM Strings
String 1: www.dell.com
Handle 0x0D00, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x0F00, DMI type 15, 29 bytes
System Event Log
Area Length: 2049 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: Memory-mapped physical 32-bit address
Access Address: 0xFFF01000
Status: Valid, Not Full
Change Token: 0x00000018
Header Format: Type 1
Supported Log Type Descriptors: 3
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: System limit exceeded
Data Format 2: System management
Descriptor 3: Log area reset/cleared
Data Format 3: None
Handle 0x1000, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 4
Handle 0x1100, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_1
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Manufacturer: AD00000000000000
Handle 0x1101, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_3
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1102, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_2
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1103, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_4
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1300, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FDFFFFFF
Range Size: 4064 MB
Physical Array Handle: 0x1000
Partition Width: 1
Handle 0x1400, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1100
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1401, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1101
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1402, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1102
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1403, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1103
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1410, DMI type 126, 19 bytes
Inactive
Handle 0x1800, DMI type 24, 5 bytes
Hardware Security
Power-On Password Status: Enabled
Keyboard Password Status: Not Implemented
Administrator Password Status: Enabled
Front Panel Reset Status: Not Implemented
Handle 0x1900, DMI type 25, 9 bytes
System Power Controls
Next Scheduled Power-on: *-* 00:00:00
Handle 0x1B10, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD00
Handle 0x1B11, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD01
Handle 0x1B12, DMI type 126, 12 bytes
Inactive
Handle 0x1B13, DMI type 126, 12 bytes
Inactive
Handle 0x1B14, DMI type 126, 12 bytes
Inactive
Handle 0x2000, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected
Handle 0x8100, DMI type 129, 8 bytes
OEM-specific Type
Header and Data:
81 08 00 81 01 01 02 01
Strings:
Intel_ASF
Intel_ASF_001
Handle 0x8200, DMI type 130, 20 bytes
OEM-specific Type
Header and Data:
82 14 00 82 24 41 4D 54 01 01 00 00 01 A5 0B 02
00 00 00 00
Handle 0x8300, DMI type 131, 64 bytes
OEM-specific Type
Header and Data:
83 40 00 83 14 00 00 00 00 00 C0 29 05 00 00 00
F8 00 4E 24 00 00 00 00 0D 00 00 00 02 00 03 00
19 04 14 00 01 00 01 02 C8 00 BD 10 00 00 00 00
00 00 00 00 FF 00 00 00 00 00 00 00 00 00 00 00
Handle 0x8800, DMI type 136, 6 bytes
OEM-specific Type
Header and Data:
88 06 00 88 5A 5A
Handle 0xD000, DMI type 208, 10 bytes
OEM-specific Type
Header and Data:
D0 0A 00 D0 01 03 FE 00 11 02
Handle 0xD100, DMI type 209, 12 bytes
OEM-specific Type
Header and Data:
D1 0C 00 D1 78 03 07 03 04 0F 80 05
Handle 0xD200, DMI type 210, 12 bytes
OEM-specific Type
Header and Data:
D2 0C 00 D2 F8 03 04 03 06 80 04 05
Handle 0xD201, DMI type 126, 12 bytes
Inactive
Handle 0xD400, DMI type 212, 242 bytes
OEM-specific Type
Header and Data:
D4 F2 00 D4 70 00 71 00 00 10 2D 2E 42 00 11 FE
01 43 00 11 FE 00 0F 00 25 FC 00 10 00 25 FC 01
11 00 25 FC 02 12 00 25 FC 03 00 00 25 F3 00 00
00 25 F3 04 00 00 25 F3 08 00 00 25 F3 0C 07 00
23 8F 00 08 00 23 F3 00 09 00 23 F3 04 0A 00 23
F3 08 0B 00 23 8F 10 0C 00 23 8F 20 0E 00 23 8F
30 0D 00 23 8C 40 A6 00 23 8C 41 A7 00 23 8C 42
05 01 22 FD 02 06 01 22 FD 00 8C 00 22 FE 00 8D
00 22 FE 01 9B 00 25 3F 40 9C 00 25 3F 00 09 01
25 3F 80 A1 00 26 F3 00 A2 00 26 F3 08 A3 00 26
F3 04 9F 00 26 FD 02 A0 00 26 FD 00 9D 00 11 FB
04 9E 00 11 FB 00 54 01 23 7F 00 55 01 23 7F 80
5C 00 78 BF 40 5D 00 78 BF 00 04 80 78 F5 0A 01
A0 78 F5 00 93 00 7B 7F 80 94 00 7B 7F 00 8A 00
37 DF 20 8B 00 37 DF 00 03 C0 67 00 05 FF FF 00
00 00
Handle 0xD401, DMI type 212, 172 bytes
OEM-specific Type
Header and Data:
D4 AC 01 D4 70 00 71 00 03 40 59 6D 2D 00 59 FC
02 2E 00 59 FC 00 6E 00 59 FC 01 E0 01 59 FC 03
28 00 59 3F 00 29 00 59 3F 40 2A 00 59 3F 80 2B
00 5A 00 00 2C 00 5B 00 00 55 00 59 F3 00 6D 00
59 F3 04 8E 00 59 F3 08 8F 00 59 F3 00 00 00 55
FB 04 00 00 55 FB 00 23 00 55 7F 00 22 00 55 7F
80 F5 00 58 BF 40 F6 00 58 BF 00 EB 00 55 FE 00
EA 00 55 FE 01 40 01 54 EF 00 41 01 54 EF 10 ED
00 54 F7 00 F0 00 54 F7 08 4A 01 53 DF 00 4B 01
53 DF 20 4C 01 53 7F 00 4D 01 53 7F 80 68 01 56
BF 00 69 01 56 BF 40 FF FF 00 00 00
Handle 0xD402, DMI type 212, 152 bytes
OEM-specific Type
Header and Data:
D4 98 02 D4 70 00 71 00 00 10 2D 2E 2D 01 21 FE
01 2E 01 21 FE 00 97 00 22 FB 00 98 00 22 FB 04
90 00 11 CF 00 91 00 11 CF 20 92 00 11 CF 10 E2
00 27 7F 00 E3 00 27 7F 80 E4 00 27 BF 00 E5 00
27 BF 40 D1 00 22 7F 80 D2 00 22 7F 00 45 01 22
BF 40 44 01 22 BF 00 36 01 21 F1 06 37 01 21 F1
02 38 01 21 F1 00 39 01 21 F1 04 2B 01 11 7F 80
2C 01 11 7F 00 4E 01 65 CF 00 4F 01 65 CF 10 D4
01 65 F3 00 D5 01 65 F3 04 D2 01 65 FC 00 D3 01
65 FC 01 FF FF 00 00 00
Handle 0xD403, DMI type 212, 157 bytes
OEM-specific Type
Header and Data:
D4 9D 03 D4 70 00 71 00 03 40 59 6D 17 01 52 FE
00 18 01 52 FE 01 19 01 52 FB 00 1A 01 52 FB 04
1B 01 52 FD 00 1C 01 52 FD 02 1D 01 52 F7 00 1E
01 52 F7 08 1F 01 52 EF 00 20 01 52 EF 10 21 01
52 BF 00 22 01 52 BF 40 87 00 59 DF 20 88 00 59
DF 00 E8 01 66 FD 00 E9 01 66 FD 02 02 02 53 BF
00 03 02 53 BF 40 04 02 53 EF 00 05 02 53 EF 10
06 02 66 DF 00 07 02 66 DF 20 08 02 66 EF 00 09
02 66 EF 10 17 02 66 F7 00 18 02 66 F7 08 44 02
52 BF 40 45 02 52 BF 00 FF FF 00 00 00
Handle 0xD800, DMI type 126, 9 bytes
Inactive
Handle 0xDD00, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 00 DD 00 01 00 00 00 10 F5 00 00 00 00 00
00 00 00
Handle 0xDD01, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 01 DD 00 01 00 00 00 11 F5 00 00 00 00 00
00 00 00
Handle 0xDD02, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 02 DD 00 01 00 00 00 12 F5 00 00 00 00 00
00 00 00
Handle 0xDE00, DMI type 222, 16 bytes
OEM-specific Type
Header and Data:
DE 10 00 DE C1 0B 00 00 10 05 19 21 01 00 00 01
Handle 0x7F00, DMI type 127, 4 bytes
End Of Table
Hdparm also does not tell me the max data transfer rate (disk speed) of my current drive although this link : www.wdc.com/en/library/sata/2879-001146.pdf says that it is 3.0Gb/s
and here's hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: WDC WD800JD-75JNC0
Firmware Revision: 06.01C06
Standards:
Supported: 6 5 4
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156250000
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 76293 MBytes
device size with M = 1000*1000: 80000 MBytes (80 GB)
cache/buffer size = 8192 KBytes
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 8
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
SET_MAX security extension
Automatic Acoustic Management feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* SMART error logging
* SMART self-test
* Gen1 signaling speed (1.5Gb/s)
* Host-initiated interface power management
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
Checksum: correct
Last edited by Inxsible (2011-03-27 04:40:49)

I just checked my BIOS and my current setting is set at IDE although it also mentions that the default should be AHCI. Currently I have a dual boot of Windows 7 (need it for Tax software) and Arch
So I guess, when I get the new HDD, I will first set it to AHCI and then install the OSes on it. See if NCQ helps any, and if not I will turn it back and re-install (if I have to). I am planning to have Windows only in virtualbox in the new drive.
Anyhoo, while I was in the BIOS I found two things which I had questions about :
1) Under Onboard Devices --> Integrated NIC , my setting is currently set at "On w/PXE" and it says the default should be just "On". Would it be ok to change it back to On since its a single machine and its not booting an OS on any server. I just don't want to have to re-install anything now since I will be doing that in the new HDD.
2) How would I know whether my BIOS would support a 64 bit OS in Virtualbox? I checked some setting under Virtualization, but they weren't very clear.
I will edit this post and let you know exactly what settings were present under the Virtualization sub-section.

Gigabit ethernet + TC doesn't mean gigabit transfer rates to the TC drive..

Alright.... I've spent a ton of time trying to figure this out (probably more than I should have) and I thought I'd post my findings so that either a) I'll save someone else time out there or b) someone can tell me I'm a complete moron
So I had an airport extreme. I replaced it with a Time Capsule. I have a Windows (boooo) PC connecting directly to my TC using a gigabit ethernet card (which I bought specifically connect it to the TC) so (I thought) I could enjoy gigabit transfer speeds to the internal hard drive from the wired PC. I had some fun plans of shoving my itunes directory on the TC and letting appletv sync (yes through my pc) and keeping lots of videos there, etc. Who cares - it'd be at gigabit speeds! But, in reality, things didn't quite work that way (though my itunes directory does still live on my TC...for now).
Well, I had a semi-unique situation to do some pretty massive testing because I have 2 gigabit network cards, 1 100mb network card, and a wireless-n network card and two internal hard drives - both very fast. I also tried Cat 5, Cat 5e, and a Cat 6 cable.
And here's what I (think I) figured out:
The hard drive in TC can not achieve gigabit transfer speeds. Your transfer rates will be limited by the IO to the hard drive. In fact, it can't even come close.
Using my "fastest" setup - so Cat 6, fastest internal drive, gigabit ethernet, and transferring a file exactly 1 gig in size I was able to have a sustained transfer rate of 140 megabit per second - that's 17.4 MB/s for folks not wanting to do the math (that's reading FROM the TC. Writing TO the TC dropped the speed down to 106 megabit/second or 13.35 MB/s). Going to a 5e cable knocked that down to 130 megabit a second. Putting in a Cat 5 cable knocked me down to 110 megabit a second. Switching between my two gigabit network cards did nothing. Switching my cards between two computers did nothing.
Now, just changing the above setup to use my 100Mb network card resulted in these results: 67 megabit read (8.4MB/s) and 65 megabit write (8MB/s)...
And using wireless N, I got about 10MB/s up and down.
And just as a final test, connecting my two computers together using the 2 gigabit network cards through the TC, I was able to achieve standard gigabit speeds.
SO what does this all mean?
I think the IO to the hard drive in the TC can only read at about 140 megabit/s and write at about 110 megabit/s. I'm not sure if it's the HD itself or how it's connecting to the TC - but that's why I'm not aware of anyone getting faster transfer rates to the drive in the TC (maybe you guys are?). The gigabit ports themselves are fine - and if you're doing anything from one gigabit port to another gigabit port you'll be fine.
So stop beating yourself up trying to find some elusive XP specific issue with gigabit transfer rates (though vista had a problem - shocker), or that you must have a defective gigabit card (which is why I have two cards now instead of one :)), or that your cable must be bad ("maybe my cat 5e isn't good enough?")... it's just this drive ... or how the drive is connecting to the network - can't handle the gigabit speeds.
Unless someone else out there has another explanation? Do these speeds mesh with what you're seeing in "optimal" situations? Or maybe there's just a throttle switch for goobers like me using Windows instead of MacOS!

Hi,
the interfaces available today which connect your drives integrated electronics to your computer can handle that speeds. but the drive itself is limited by the mechanical things going on in there
You can get such transfer speeds if the data you request is in the cache of the drives internal electronics for example. Some drives have 8 MB of cache memory. So if you request to read or write less than 8 mb and (in the read case) you are lucky enough to have those few megabytes cached then you may get that performance
Regards,
somi

Determining Data transfer rate through modem in java

Hi,
I want to write an application in java which will communicate with
connected modem of the system and it will detect the data transfer rate.
I want to know how much data is transferring(upload/download)through modem and in a specific time how much data is transferred.
I will give some max upload/downloading limit for a specific time and if data transfer exceeds that limit,it will show message.
e.g if i fix max upload/download data transfer limit by the modem is say 10GB/20GB for a specific time span say for 15 days.Then my program automatically will start when the Modem will be connected and keep a log of data transfer(upload/download)and if data transfer goes beyond limit then it will show message.Also i would be able to see how much data is transferred for any specific day.
I want to know this type of application is possible in java.If yes then
which API's i need to use.
If this type of program is available in some site in other language then also i will be helpful.Pl give the links.
byeeeeeeee
Pradipto

Hi,
i want to do it in java only to explore the power of
java.I agree with Abuse, Java is not designed for such applications. I'm not even sure if you can solve your problems with Java.

FTP/SFTP/FISH (etc) slow file transfer rate over LAN

Hi everyone,
I have a problem with transferring files over my home network that has been bothering me for quite some time.
I have a 802.11n router which should provide me with the transfer rate up to 150 Mbps (afaik). When I download files from the Internet, 3 MB/s data transfer rate is of no problem.
However, when receiving or sending data over LAN, the transfer rate is much slower (1.8 MB/s).
My rough guess is (after reading some papers on this topic) that TCP protocol is causing this (its flow control feature to be exact), since TCP max window size is too small on Linux by default.
So, setting TCP max window size to a greater number should solve this.
I tried putting this:
# increase TCP max buffer size setable using setsockopt()
# 16 MB with a few parallel streams is recommended for most 10G paths
# 32 MB might be needed for some very long end-to-end 10G or 40G paths
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
# increase Linux autotuning TCP buffer limits
# min, default, and max number of bytes to use
# (only change the 3rd value, and make it 16 MB or more)
net.ipv4.tcp_rmem = 4096 87380 16777216
net.ipv4.tcp_wmem = 4096 65536 16777216
# recommended to increase this for 10G NICS
net.core.netdev_max_backlog = 30000
# these should be the default, but just to be sure
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_sack = 1
in /etc/sysctl.conf but to no avail.
So either there is no problem with the max window size setting, or the Linux kernel ignores it (maybe because /proc is no longer supported?).
Thanks for any neat ideas.
Last edited by Vena (2012-06-01 21:48:14)

Bump? No ideas whatsoever?

Disk data transfer rate - iMac 2013

Good morning Apple fellows
First of all, sorry for my troubled English speaking, I'll do my best to explain the issue I'm having in the best way possible.
Yesterday I finally received my new iMac (I'm a proud Apple user since 2006), the machine has these specifications: 16 GB Ram, i7 processor, nVidia GT 780M, and a SSD drive of 1TB of capacity.
Under Mavericks everything runs smooth and fine, no issues at all, just perfect, the fastest machine I've ever had. Unfortunately, I had to install Windows 7 via Bootcamp (I'm a mechanical engineer and I use Autodesk Inventor to do my stuff).
After completing the installation of the Microsoft OS, I instantly noticed some laggy performance while running Windows: I installed as asked all the Bootcamp drivers with the USB pendrive that I prepared, but both the startup of the system and the normal use were a bit slow, even slower than my old '09 iMac.
In order to understand what the problem was, I ran the system performance test included in Windows: all the ratings I have are maxed out at 7.9 (7.9 is the top I think), in exception of the "Disk Data Transfer Rate", that is 5.9. As far as I remember, this value is typical for a mechanical disk drive, not for an SSD drive supported with PCIe connections.
Does anybody here got a similar issue? Is there any driver package that I have to install in addition to the Bootcamp drivers?
Thanks in advance

That is because the WEI uses your boot disk as the default device to measure performance, and, for instance, a Velociraptor 10 K disk, does not score more than 5.9. The story changes when the test is run on other disks, like my array:
However, this measurement is totally worthless in real life. You should look at practical benchmarks like PPBM5 Benchmark

Slow Wireless and Erratic Transfer Rate

Alright, I just got a new Macbook Pro 15 inch last week because my iBook G4 kicked the bucket... again.
All has been well except for wireless. Any Wifi spot has had horrible transfer rates. The TX Rate goes up and down from 54/54 Mbits/sec to 0/54 MBits/sec over and over. This affects local transfer speeds (horribly slow), download speeds and even makes websites not load the first try.
It isn't the router being bad as I've confirmed the problem on more than one router and this is the only computer with the problem on all routers. An Intel iMac with the same (I think anyway) wireless-n card has no trouble at all either with the TX Rate to the same base station.
I tried booting into Windows (XP Professional SP2) but I can't seem to find any utilities to give me as detailed wifi information as AP Grapher does. It was hard to tell if there was a difference.
So is my wifi card at fault here, or OS X? This is a big issue for me and I can't seem to find any solutions online. Also giving a link to AP Grapher to show the TX Rate (the white line) going nuts.
http://socamx.net/tmp/apgrapher.png

i've got mbp with 10.4.11, that just started SLOWING down madly today..after all the research i see many have it much worse with complete loss of wifi...but this is HORRIBLE
i ran a speed test of IBM laptop side by side with MBP and downstream difference was 3X
HELP!

How to get better than 5.2MB/s transfer rate from USB 2.0 on Mac Mini

G'day,
I've got a circa 2007 Mac Mini with 1GB of RAM, running Snow Leopard. Connected to this is a USB 2.0 500GB Seagate Freeagent drive from circa 2008. As far as I know, the USB disk is free of errors.
I am trying to use dd with a block size of 1MB to transfer a 250GB file from an Ethernet mounted Time Capsule drive to the USB disk on /dev/disk1.
A dd from the Time Capsule to the /dev/null gives me a transfer rate of ~35-40MB/s. However, when the target is /dev/disk1, the transfer rate is only around 5MB/s. I checked the system profiler and disk1 is connected to the USB High Speed Bus.
Any clues on how to improve USB 2.0 transfer performance?

Fragmentation is unlikely to be an issue since I was trying to write to the raw block device with dd which is as close to a pure sequential write scenario as one is likely to encounter (e.g. no small block, random access involved)
From a Linux host, I was able to dd to a file on the disk's file system at 20MB/s.
I'll run some other tests with another disk to see whether the issue is peculiar to the disk or to the Mac's USB subsystem.

Solaris 10 u5 Samba slow transfer rates?

Hi!
I've installed Solaris 10 x86 (Core2Duo - x64) server, with Samba over ZFS RAID-Z. Samba is a part of Active Directory Domain. I've managed to join it to domain, to get the users and groups from A.D. and to translate them to Unix IDs. Everything works really good. Samba is installed from the packages from Solaris 10 DVD.
Only problem I have is the performance :( It's disastrous!
On 100Mbit Realtek NIC, Samba can manage around 4 MB/s if log level is set to very high (10). If I lower it to 0, then transfer rates go up to 7.5-8.5MB/s and they fluctuate in that interval.
On the same network, there is a Debian Samba server, and transfer rates go high as 10.5-11.0MB/s.
Next test I did was switching to Gbit interface. That increased transfer rates up to 25 MB/s, but that is still 5 times slower than the theoretical limit.
So, next thing I've tried was to switch to Blastwave (CSW) Samba instead of SUNW Samba.... My transfer rates went back to normal immediately! It was a bit of shock for me... I could transfer about 10MB/s on 100Mbit interface, and around 45MB/s on 1Gbit interface. 45MB/s is theoretically limit of the workstation hard drive I was doing transfers from.
Sun packaged (SUNW) Samba is 3.0.28 patched today to the latest patchlevel, and CSW uses 3.0.23. I used CSW Samba with the exact same smb.conf file. Only problem is - I never managed to connect CSW samba to ADS on my network :( So I gave up on that, and I'm facing a dilemma. Managers request full speed of the Samba server (comparable to Linux/Windows shares), but I just can't connect to Domain with CSW package.
So I'm asking you guys - any ideas what could be the problem with SUNW Samba and performance? Is it just the 3.0.28 vs 3.0.23 issue, or what? Why is there so big difference in transfer rates? :(
Please help!

OK, here goes my smb.conf:
[global]
workgroup = MYCOMPANY
realm = MYCOMPANY.LOCAL
server string = server4 (Samba, Solaris 10)
security = ADS
map to guest = Bad User
obey pam restrictions = Yes
password server = server1.mycompany.local
passdb backend = tdbsam
log file = /var/samba/log/log.%m
max log size = 50
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE
load printers = No
local master = No
domain master = No
dns proxy = No
idmap uid = 10000-90000
idmap gid = 10000-90000
winbind separator = +
winbind enum users = Yes
winbind enum groups = Yes
winbind use default domain = Yes
[share]
comment = Share on ZFS Raid-Z
path = /tank/share
force user = local_user
force group = users
read only = No
guest ok = Yes
vfs objects = zfsacl

Clients Connect to N AP's on 5508 and get different Transfer rates than on 4404

I have have 2x 4404's (2x) and 2x 5508's all are running 7.0.240.0. When I take an 1142 and associate it to a 4404 I can connect a test client using N at 144Mbps and I can get transfer rates averaging 70Mbps (using iperf tests). When I take the same AP and associate it to a 5508, (same SSID, etc) I connect at 144Mbps but only get average 6Mbps transfer rates. I get the same results with 1252's. I get the same results if I wipe the config on the 5508 and start from scratch. It only happens when connecting at a/n, when I use a b/g AP such as 1132 I connect at 54Mbps on either controller and get transfer rates of 24Mbps. I have enabled disabled LAG (rebooted), moved the 5508 to connect to the same swtich ports, swapped GBICs. The issue happens on both 5508s, TAC has been unable to resolve this and they are confused as well.
Some of the other things I have tried:
•-          You are facing the issue on 5508's WLC only.
•-          Both the WLC and the client reports high connection speed “144Mbps”
•-          iPerf between wireless and wired showed the following:
on 4400: [124] 0.0-16.9 sec   154 MBytes 76.5 Mbits/sec
On 5500: [124] 0.0-94.3 sec 70.2 MBytes 6.25 Mbits/sec
•-          The AP is the same AP, you just bounce it from 1 WLC to another.
•-          The location of the AP is the same in all the tests, but it can be replicated with an 1142 anywhere on site and get the same results.
•-          The test PC is the same in both cases
•-          The configuration is the same on both WLC’s confirmed visaully in GUI and via CLI outputs and compaired.
•-          The switch is the same, but have tired swapping 4404 and 5508 in data center.
•-          Tried to swap the GBICs.
•-          Used different ports on the 5508 (not just diff GBICs)
•-          Disabled the LAG to rule out the load balancing algorithm.
•-       Replaced the patch cables
Used same ip space that the 4404 is using without sucess.
Upgraded my second 5508 to version 7.5 and exact same resutls.
Any ideas?

Hi
In my 5508 WLC i have exactly the same problem as you gsutherland
I tried apply this command config 802.11b 11nSupport a-mpdu tx priority all disable
and i get message
"802.11b network not disabled"
Why i must turn off b standard ?
Thanks for respons

Change data transfer rate ?

Hi there,
I have installed a new WD 1tb internal hard drive in my late 2006 iMac . I've managed to get over a problem I posted about earlier namely getting the Snow Leopard disc out and using my original Tiger 10.4 discs. Trouble now is despite following the instructions for formatting my new hard drive I keep getting input\output error coming up . I've googled a lot and I believe it may be because my intel Mac supports 1.5gbs a second transfer rate whilst the hard drive is 6gbs . I have a caviar blue advanced drive that has no jumpers to change , but I'm led to believe that would be the answer . I'm relatively new to all this but are there jumpers in the mac itself ? Or is there a way to change the rate so my Mac accepts and formats the drive ? On various sites it says the drive is compatible but not how to do this. Hope it makes sense lads I'm sooo stressed .
Cheers

Transfer rate won't cause this problem. Your Mac will only transfer data as fast/slow as it can, 1.5gbs. The HD transfer rate will automatically slow to 1.5gbs.
What did you use to format the HD and what format did you use? It should be formatted to 'Mac OS Extended (Journaled)'. This can be easily done using the Disk Utility app that comes with OSX.
Usually the jumpers are for making the HD a master or slave drive. You shouldn't have to mess with the new HD settings to make it work.

RT to HOST transfer rate problem in cRIO-9073 ?

Similar Messages

Maybe you are looking for