博客
关于我
STM32F7 LWIP协议栈TCP速度测试
阅读量:596 次
发布时间:2019-03-12

本文共 3152 字,大约阅读时间需要 10 分钟。

Comparing TCP Reception Performance Between LWIP and DJYIP Protocol Stacks on STM32F7

When evaluating the performance of the LWIP and DJYIP protocol stacks on STM32F7, it is important to understand the differences in TCP packet reception speeds under various conditions. This testing was conducted to ensure consistent hardware and software configurations while assessing the efficiency of the protocol stacks. The following analysis outlines the testing methodology, setup, and results.

Testing Objectives

The primary goal of this testing was to compare the TCP packet reception speeds of the LWIP and DJYIP protocol stacks under identical hardware and software conditions. By maintaining consistency in both hardware platforms and software configurations, we aimed to isolate any differences in performance that could be attributed to the protocol stacks themselves.

Testing Methodology

The testing was conducted using an STM32F7 development board with the following specifications:

  • Hardware Platform: STM32756G-EVAL2
  • Clock Frequency: 200MHz
  • Communication Interface: Direct connection to the sender board

The software configuration for both protocol stacks included:

  • Network Driver Mode: Interrupt-based
  • Buffer Pool Size: 16k bytes
  • TCP Window Size: 2048 bytes (2 * TCP MSS)

The testing process involved:

  • Code Modification: Adjusting the protocol stack configurations in lwipopts.h to optimize for high-throughput performance.
  • Client-Sender Configuration: Implementing a loop to continuously send TCP packets with varying sizes (64 to 1460 bytes).
  • Server-Receiver Configuration: Setting up a receiver loop to capture incoming data and calculate packet reception rates.
  • Testing Results

    The test results revealed significant differences between the two protocol stacks, particularly in terms of TCP reception performance:

    Data Package Size (Bytes) LWIP Reception Speed (Mbps) DJYIP Reception Speed (Mbps)
    1400 3.02 3.18
    1024 4.22 3.16
    512 3.07 3.16
    256 2.02 2.5
    128 0.2±0.2 1.76
    64 0.2±0.2 1.12
    Random (0-1460) 1M (within variation) 2.52

    These results indicate that the LWIP protocol stack generally outperformed the DJYIP stack, particularly for packet sizes of 1024 bytes and larger. It is worth noting that the performance difference for 1024-byte packets might be due to the way LWIP handles packets of sizes that are powers of two, which could be a coincidence or a reflection of underlying characteristics of the protocol stack.

    Implications for Network Performance

    The findings suggest that the choice of protocol stack can significantly impact TCP performance, especially under varying packet size conditions. While LWIP demonstrated slightly better performance for larger packets, it is crucial to consider the specific requirements of the application when selecting a protocol stack. DJYIP, while slightly less efficient for larger packets, might provide more predictable or consistent performance in certain scenarios.

    Future testing could explore additional factors such as packet fragmentation, lower-layer driver optimizations, and network hardware configurations to further refine the performance characteristics of these protocol stacks.

    转载地址:http://kszxz.baihongyu.com/

    你可能感兴趣的文章
    MySQL函数(转发)
    查看>>
    mysql分区表
    查看>>
    MySQL分层架构与运行机制详解
    查看>>
    mysql分库分表中间件简书_MySQL分库分表
    查看>>
    MySQL分库分表会带来哪些问题?分库分表问题
    查看>>
    MySQL分组函数
    查看>>
    MySQL分组查询
    查看>>
    Mysql分表后同结构不同名称表之间复制数据以及Update语句只更新日期加减不更改时间
    查看>>
    mySql分页Iimit优化
    查看>>
    MySQL分页查询
    查看>>
    mysql列转行函数是什么
    查看>>
    mysql创建函数报错_mysql在创建存储函数时报错
    查看>>
    mysql创建数据库和用户 并授权
    查看>>
    mysql创建数据库指定字符集
    查看>>
    MySql创建数据表
    查看>>
    MySQL创建新用户以及ERROR 1396 (HY000)问题解决
    查看>>
    MySQL创建用户与授权
    查看>>
    MySQL创建用户报错:ERROR 1396 (HY000): Operation CREATE USER failed for 'slave'@'%'
    查看>>
    MySQL创建索引时提示“Specified key was too long; max key length is 767 bytes”
    查看>>
    mysql初始密码错误问题
    查看>>