Skip to content

telcoware/h2simple

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

56 Commits

docs

docs

 
 

h2sim

h2sim

 
 

Makefile

Makefile

 
 

genkey_ec.sh

genkey_ec.sh

 
 

genkey_rsa.sh

genkey_rsa.sh

 
 

h2cli.c

h2cli.c

 
 

h2svr.c

h2svr.c

 
 

Repository files navigation

h2sim - HTTP2 Simple Application Framework

For 3GPP R15 5G SBI HTTP/2 NF Simulator in C using nghttp2. By Lee Yongjae, Telcoware,Inc., setup74@telcoware.com, Version: 0.2.1 at 2019-03-13. See: https://github.com/setup74/h2simple

Introduction

Nghttp2 has as nice event modeled C api, but the http client/server codes in pacakge are built on C++/boost, not for clean C users.

So a HTTP2 stack layer for standalone C is built, named http2simple. And goes with client and server simulator example codes.

Files

h2sim library example application:

  • h2cli.c h2svr.c: h2sim app example code for client and server simulator
  • NOTE: use -DTLS_MODE=1 option to be built with openssl library (default)

h2sim library files:

  • h2.h: the h2sim API defintion
  • h2_priv.h: h2sim library private header; NOT FOR APPLICATION
  • h2_msg.c, h2_sess.c, h2_io.c: h2sim library implementation

tls utilities:

  • genkey_ex.sh: generates eckey.pem, eccert.pem
  • genkey_rsa.sh: generates rsakey.pem, rsacert.pem

Build

need nghttp2 installed:

  • env variable NGHTTP2_INCDIR and NGHTTP2_LIBDIR should be set if nghttp2 is not installed in /usr/local/

run make:

  • h2sim/libh2sim.a, h2svr and h2cli are built

run genkey_ec.sh:

  • eckey.pem and eccert.pem are generated to be used for tls mode default key and certificate file

Abbrevations

  • h2: http2
  • nv: name value
  • wr: write
  • rd: read
  • hdr: header
  • msg: message
  • req: request
  • rsp: response
  • prm: promise
  • strm: stream
  • sess: session
  • ctx: context

h2cli and h2svr Run Examples

server with response cases:

./h2svr -S http://0.0.0.0:8080 -S https://0.0.0.0:8081 \
  -m POST   -p /user/ -s 200 \
            -x content-type=application/json -t '{ "RESULT" : "SUCCESS" }' \
  -m GET    -p /user/ -s 200 \
            -x content-type=application/json -t '{ "USER_NAME" : "somebody" }' \
  -m DELETE -p /user/ -s 200 \
  -m GET    -p /user2/ -s 404

server with reponse cases and push promise:

./h2svr -S http://0.0.0.0:8080 -S https://0.0.0.0:8081 \
  -m POST -p /user1k/ -s 200 -x content-type=application/json -e 1k \
     -o /user1k/name1 -s 200 -x content-type=application/json -t '1k_name1' \
     -o /user1k/name2 -s 200 -x content-type=application/json -t '1k_name2' \
     -o /user1k/name3 -s 200 -x content-type=application/json -t '1k_name3' \
  -m POST -p /user4k/ -s 200 -x content-type=application/json -e 4k \
     -o /user4k/name1 -s 200 -x content-type=application/json -t '4k_name1' \
     -o /user4k/name2 -s 200 -x content-type=application/json -t '4k_name2' \
     -o /user4k/name3 -s 200 -x content-type=application/json -t '4k_name3' \
  -m POST -p /user10k/ -s 200 -x content-type=application/json -e 10k \
     -o /user10k/name1 -s 200 -x content-type=application/json -t '10k_name1' \
     -o /user10k/name2 -s 200 -x content-type=application/json -t '10k_name2' \
     -o /user10k/name3 -s 200 -x content-type=application/json -t '10k_name3'

client single uri GET case (default method is 'GET'):

./h2cli http://127.0.0.1:8080/user1k/nobody:

client single uri request with method and user header:

./h2cli -m POST -u http://127.0.0.1:8080/test.txt \
    -x content-type=application/json -f your_request_body_file

client single uri request with request symbol replacement on uri, hdr, body:

./h2cli -R __MDN__=01092%06d \
  -m POST -u http://127.0.0.1:8080/user/__MDN__  \
          -x content-type=application/json -t '{ "USER_MDN" : "__MDN__" }'

client multiple request senario:

./h2cli -R __MDN__=01092%06d -s http -a 127.0.0.1:8080 \
  -m POST   -p /user/__MDN__  \
            -x content-type=application/json -t '{ "USER_MDN" : "__MDN__" }'  \
  -m GET    -p /user/__MDN__  \
  -m DELETE -p /user/__MDN__

client loop case:

-P req_par for concurrent streams (max:100) -C req_max for request loop count -q suppress output for performance check

./h2cli -P 100 -C 100000 -m GET -u http://127.0.0.1:8080/user1k/nobody

h2cli and h2svr Performance Tests

server for 1k/4k/10k performance test:

./h2svr -S http://0.0.0.0:8080 -S https://0.0.0.0:8081 \
  -m POST -p /user1k/ -s 200 -x content-type=application/json -e 1k \
  -m POST -p /user4k/ -s 200 -x content-type=application/json -e 4k \
  -m POST -p /user10k/ -s 200 -x content-type=application/json -e 10k \
  -q

client for tcp 1k/4k/10k performance test:

./h2cli -P 100 -C 100000 -R __MDN__=01092%06d      \
  -m POST -u http://127.0.0.1:8080/user1k/__MDN__    \
          -x content-type=application/json -e 1k -q; \
./h2cli -P 100 -C 100000 -R __MDN__=01092%06d      \
  -m POST -u http://127.0.0.1:8080/user4k/__MDN__    \
          -x content-type=application/json -e 4k -q; \
./h2cli -P 100 -C 100000 -R __MDN__=01092%06d      \
  -m POST -u http://127.0.0.1:8080/user10k/__MDN__   \
          -x content-type=application/json -e 10k -q

TCP 1K/4K/10K TPS:

  • 120K/80K/55K LOCAL on A: Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz
  • 80K/55K/33K LOCAL on B: Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz (HT=off)
  • 73K/18K/7K REMOTE A->B

client for tls 1k/4k/10k performance test:

./h2cli -P 100 -C 100000 -R __MDN__=01092%06d      \
  -m POST -u https://127.0.0.1:8081/user1k/__MDN__   \
          -x content-type=application/json -e 1k -q; \
./h2cli -P 100 -C 100000 -R __MDN__=01092%06d      \
  -m POST -u https://127.0.0.1:8081/user4k/__MDN__   \
          -x content-type=application/json -e 4k -q; \
./h2cli -P 100 -C 100000 -R __MDN__=01092%06d      \
  -m POST -u https://127.0.0.1:8081/user10k/__MDN__  \
          -x content-type=application/json -e 10k -q

TLS 1K/4K/10K TPS:

  • 55K/44K/33K LOCAL on A: Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz
  • 35K/30K/22K LOCAL on B: Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz (HT=off)
  • 65K/19K/7K REMOTE A->B

h2cli and h2svr Tests with Certificate Verify

server for 1k/4k/10k performance test:

./h2svr_r \
  -k pse_telco/nf2_svr.key  \
  -c pse_telco/nf2_svr.crt  \
  -V verify,trust_dir=pse_telco/certs,crl,crl_all,purpose \
  -S http://0.0.0.0:8080 -S https://0.0.0.0:8081 \
  -m POST -p /user1k/ -s 200 -x content-type=application/json -e 1k \
  -m POST -p /user4k/ -s 200 -x content-type=application/json -e 4k \
  -m POST -p /user10k/ -s 200 -x content-type=application/json -e 10k \
  -q

client for tls 1k/4k/10k performance test:

./h2cli_r \
  -P 100 -C 100000 -R __MDN__=01092%06d \
  -k pse_star/nf1_cli.key      \
  -c pse_star/nf1_cli.crt      \
  -V verify,trust_dir=pse_star/certs,crl,crl_all,purpose \
  -m POST -u https://127.0.0.1:8081/user4k/__MDN__   \
          -x content-type=application/json -e 4k -q

h2cli and h2svr HTTP/1.1 Performance Tests

server for 1k/4k/10k performance test:

./h2svr_r -1 -S http://0.0.0.0:8080 -S https://0.0.0.0:8081 \
  -m POST -p /user1k/ -s 200 -x content-type=application/json -e 1k \
  -m POST -p /user4k/ -s 200 -x content-type=application/json -e 4k \
  -m POST -p /user10k/ -s 200 -x content-type=application/json -e 10k \
  -q

client for HTTP/1.1 tcp 1k/4k/10k performance test:

./h2cli_r -1 -P 100 -C 100000 -R __MDN__=01092%06d      \
  -m POST -u http://127.0.0.1:8080/user1k/__MDN__    \
          -x content-type=application/json -e 1k -q; \
./h2cli_r -1 -P 100 -C 100000 -R __MDN__=01092%06d      \
  -m POST -u http://127.0.0.1:8080/user4k/__MDN__    \
          -x content-type=application/json -e 4k -q; \
./h2cli_r -1 -P 100 -C 100000 -R __MDN__=01092%06d      \
  -m POST -u http://127.0.0.1:8080/user10k/__MDN__   \
          -x content-type=application/json -e 10k -q

HTTP/1.1 TCP 1K/4K/10K TPS:

  • 160K/120K/90K LOCAL on A: Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz

client for HTTP/1.1 tls 1k/4k/10k performance test:

./h2cli_r -1 -P 100 -C 100000 -R __MDN__=01092%06d      \
  -m POST -u https://127.0.0.1:8081/user1k/__MDN__   \
          -x content-type=application/json -e 1k -q; \
./h2cli_r -1 -P 100 -C 100000 -R __MDN__=01092%06d      \
  -m POST -u https://127.0.0.1:8081/user4k/__MDN__   \
          -x content-type=application/json -e 4k -q; \
./h2cli_r -1 -P 100 -C 100000 -R __MDN__=01092%06d      \
  -m POST -u https://127.0.0.1:8081/user10k/__MDN__  \
          -x content-type=application/json -e 10k -q

HTTP/1.1 TLS 1K/4K/10K TPS:

  • 90K/70K/49K LOCAL on A: Intel(R) Xeon(R) Gold 6132 CPU @ 2.60GHz

About

HTTP2 Simple Application Framework for 3GPP R15 5G SBI HTTP/2 HTTP/1.1 NF Simulator in C using nghttp2

Topics

c application framework simulator http2 nghttp2 3gpp sbi

Resources

Readme
Activity
Custom properties

Stars

7 stars

Watchers

1 watching

Forks

4 forks
Report repository

Releases

No releases published

Packages

No packages published

Languages