对expat库XML_Parse函数调用优化的测试

xpat库文档中说

复制代码
XML_Parse
enum XML_Status XMLCALL
XML_Parse(XML_Parser p,
          const char *s,
          int len,
          int isFinal);
enum XML_Status {
  XML_STATUS_ERROR = 0,
  XML_STATUS_OK = 1
};
Parse some more of the document. The string s is a buffer containing part (or perhaps all) of the document. The number of bytes of s that are part of the document is indicated by len. This means that s doesn't have to be null-terminated. It also means that if len is larger than the number of bytes in the block of memory that s points at, then a memory fault is likely. Negative values for len are rejected since Expat 2.2.1. The isFinal parameter informs the parser that this is the last piece of the document. Frequently, the last piece is empty (i.e. len is zero.)

If a parse error occurred, it returns XML_STATUS_ERROR. Otherwise it returns XML_STATUS_OK value. Note that regardless of the return value, there is no guarantee that all provided input has been parsed; only after the concluding call will all handler callbacks and parsing errors have happened.

Simplified, XML_Parse can be considered a convenience wrapper that is pairing calls to XML_GetBuffer and XML_ParseBuffer (when Expat is built with macro XML_CONTEXT_BYTES defined to a positive value, which is both common and default). XML_Parse is then functionally equivalent to calling XML_GetBuffer, memcpy, and XML_ParseBuffer.

To avoid double copying of the input, direct use of functions XML_GetBuffer and XML_ParseBuffer is advised for most production use, e.g. if you're using read or similar functionality to fill your buffers, fill directly into the buffer from XML_GetBuffer, then parse with XML_ParseBuffer.

最后两段说,这个函数其实是XML_GetBuffer和XML_ParseBuffer两个函数的包装,再在中间插入从用户buffer到parser buffer的复制,如果read函数直接用parser buffer当缓冲区,就可以省略memcpy的操作。

我用先前的xml文件转csv程序做了个测试,

原代码expatfile.c调用XML_Parse

c 复制代码
    char buffer[8192];
    int done;
    do {
        size_t len = fread(buffer, 1, sizeof(buffer), file);
        done = (len < sizeof(buffer));
  
        if (XML_Parse(parser, buffer, len, done) == XML_STATUS_ERROR) {
            break;
        }
    } while (!done);

修改后expatfile2.c调用XML_GetBuffer和XML_ParseBuffer

c 复制代码
    char buffer[8192];
    int done;
    do {void *buff = XML_GetBuffer(parser, 8192);
        size_t len = fread(buff, 1, 8192, file);
        done = (len < 8192);
  
        if (XML_ParseBuffer(parser, len, done) == XML_STATUS_ERROR) {
            break;
        }
    } while (!done);

编译运行

cmd 复制代码
gcc expatfile.c -o expatfile -lexpat -O3

time ./expatfile /par/lineitem/xl/worksheets/sheet1.xml A1:P1000000
CSV已保存到 /par/lineitem/xl/worksheets/sheet1.csv

real	0m18.882s
user	0m18.168s
sys	0m0.324s

gcc expatfile2.c -o expatfile2 -lexpat -O3

time ./expatfile2 /par/lineitem/xl/worksheets/sheet1.xml A1:P1000000
CSV已保存到 /par/lineitem/xl/worksheets/sheet1.csv

real	0m18.909s
user	0m18.116s
sys	0m0.284s

测试证明,两种调用几乎没有差别,也许现在memcpy很快,体现不出来影响了。

相关推荐
枕星而眠25 分钟前
Linux 四大进程/线程同步锁详解:互斥锁、读写锁、条件变量、文件锁
linux·c语言·后端·ubuntu·学习方法
社交怪人1 小时前
【数字对调】信息学奥赛一本通C语言解法(题号2070)
c语言·开发语言
hef2881 小时前
C语言中char指针与数组的区别及应用
c语言·开发语言
__Benco2 小时前
创建一个 Linux5.10 普通 kill 无效的守护进程 Daemon-demo
c语言
为何创造硅基生物4 小时前
C 语言 typedef 结构体私有化
c语言·开发语言·算法
潜创微科技5 小时前
IT68353:双DP 1.4 + HDMI 2.0 + USB‑C 三合一转 HDMI 2.0 单芯片KVM切换方案
c语言·开发语言
我命由我123455 小时前
C++ - 面向对象 - 析构函数
android·c语言·开发语言·c++·visualstudio·visual studio·android runtime
科芯创展8 小时前
XZ4086E,1.5A,22V,开关降压3节锂电充电芯片
c语言
科芯创展9 小时前
XZ4058B/C,20V,外置MOS,8.4V/8.7V开关充电芯片
c语言·开发语言
学困昇9 小时前
Linux 动静态库制作与原理:从 .a、.so 到 ELF 加载一次讲透
linux·运维·服务器·c语言·开发语言·c++·人工智能