首页 文章

如何使用cURL一次测量请求和响应时间?

提问于
浏览
467

我有一个Web服务,它以JSON格式接收数据,处理数据,然后将结果返回给请求者 .

我想使用 cURL 来衡量请求,响应和总时间 .

我的示例请求如下:

curl -X POST -d @file server:port

我目前在Linux中使用 time 命令测量它:

time curl -X POST -d @file server:port

时间命令只测量总时间 - 这不是我想要的 .

有没有办法使用 cURL 来衡量请求和响应时间?

10 回答

  • 4

    这是一个重复击中同一台服务器的Bash单行程序:

    for i in {1..1000}; do curl -s -o /dev/null -w "%{time_total}\n" http://server/get_things; done
    
  • 1205

    嘿比Apache Bench更好,SSL的问题更少

    ./hey https://google.com -more
    Summary:
      Total:    3.0960 secs
      Slowest:  1.6052 secs
      Fastest:  0.4063 secs
      Average:  0.6773 secs
      Requests/sec: 64.5992
    
    Response time histogram:
      0.406 [1] |
      0.526 [142]   |∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎
      0.646 [1] |
      0.766 [6] |∎∎
      0.886 [0] |
      1.006 [0] |
      1.126 [0] |
      1.246 [12]    |∎∎∎
      1.365 [32]    |∎∎∎∎∎∎∎∎∎
      1.485 [5] |∎
      1.605 [1] |
    
    Latency distribution:
      10% in 0.4265 secs
      25% in 0.4505 secs
      50% in 0.4838 secs
      75% in 1.2181 secs
      90% in 1.2869 secs
      95% in 1.3384 secs
      99% in 1.4085 secs
    
    Details (average, fastest, slowest):
      DNS+dialup:    0.1150 secs, 0.0000 secs, 0.4849 secs
      DNS-lookup:    0.0032 secs, 0.0000 secs, 0.0319 secs
      req write:     0.0001 secs, 0.0000 secs, 0.0007 secs
      resp wait:     0.2068 secs, 0.1690 secs, 0.4906 secs
      resp read:     0.0117 secs, 0.0011 secs, 0.2375 secs
    
    Status code distribution:
      [200] 200 responses
    
  • 26

    另一个可能是命令行中最简单的选项是添加内置的 --trace-time 选项:

    curl -X POST -d @file server:port --trace-time
    

    即使它在技术上不输出OP请求的各个步骤的时序,它也会显示请求的所有步骤的时间戳,如下所示 . 使用它,您可以(相当容易地)计算每个步骤花费的时间 .

    $ curl https://www.google.com --trace-time -v -o /dev/null
    13:29:11.148734 * Rebuilt URL to: https://www.google.com/
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
      0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     013:29:11.149958 *   Trying 172.217.20.36...
    13:29:11.149993 * TCP_NODELAY set
    13:29:11.163177 * Connected to www.google.com (172.217.20.36) port 443 (#0)
    13:29:11.164768 * ALPN, offering h2
    13:29:11.164804 * ALPN, offering http/1.1
    13:29:11.164833 * successfully set certificate verify locations:
    13:29:11.164863 *   CAfile: none
      CApath: /etc/ssl/certs
    13:29:11.165046 } [5 bytes data]
    13:29:11.165099 * (304) (OUT), TLS handshake, Client hello (1):
    13:29:11.165128 } [512 bytes data]
    13:29:11.189518 * (304) (IN), TLS handshake, Server hello (2):
    13:29:11.189537 { [100 bytes data]
    13:29:11.189628 * TLSv1.2 (IN), TLS handshake, Certificate (11):
    13:29:11.189658 { [2104 bytes data]
    13:29:11.190243 * TLSv1.2 (IN), TLS handshake, Server key exchange (12):
    13:29:11.190277 { [115 bytes data]
    13:29:11.190507 * TLSv1.2 (IN), TLS handshake, Server finished (14):
    13:29:11.190539 { [4 bytes data]
    13:29:11.190770 * TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
    13:29:11.190797 } [37 bytes data]
    13:29:11.190890 * TLSv1.2 (OUT), TLS change cipher, Client hello (1):
    13:29:11.190915 } [1 bytes data]
    13:29:11.191023 * TLSv1.2 (OUT), TLS handshake, Finished (20):
    13:29:11.191053 } [16 bytes data]
    13:29:11.204324 * TLSv1.2 (IN), TLS handshake, Finished (20):
    13:29:11.204358 { [16 bytes data]
    13:29:11.204417 * SSL connection using TLSv1.2 / ECDHE-ECDSA-CHACHA20-POLY1305
    13:29:11.204451 * ALPN, server accepted to use h2
    13:29:11.204483 * Server certificate:
    13:29:11.204520 *  subject: C=US; ST=California; L=Mountain View; O=Google LLC; CN=www.google.com
    13:29:11.204555 *  start date: Oct  2 07:29:00 2018 GMT
    13:29:11.204585 *  expire date: Dec 25 07:29:00 2018 GMT
    13:29:11.204623 *  subjectAltName: host "www.google.com" matched cert's "www.google.com"
    13:29:11.204663 *  issuer: C=US; O=Google Trust Services; CN=Google Internet Authority G3
    13:29:11.204701 *  SSL certificate verify ok.
    13:29:11.204754 * Using HTTP2, server supports multi-use
    13:29:11.204795 * Connection state changed (HTTP/2 confirmed)
    13:29:11.204840 * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
    13:29:11.204881 } [5 bytes data]
    13:29:11.204983 * Using Stream ID: 1 (easy handle 0x55846ef24520)
    13:29:11.205034 } [5 bytes data]
    13:29:11.205104 > GET / HTTP/2
    13:29:11.205104 > Host: www.google.com
    13:29:11.205104 > User-Agent: curl/7.61.0
    13:29:11.205104 > Accept: */*
    13:29:11.205104 > 
    13:29:11.218116 { [5 bytes data]
    13:29:11.218173 * Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
    13:29:11.218211 } [5 bytes data]
    13:29:11.251936 < HTTP/2 200 
    13:29:11.251962 < date: Fri, 19 Oct 2018 10:29:11 GMT
    13:29:11.251998 < expires: -1
    13:29:11.252046 < cache-control: private, max-age=0
    13:29:11.252085 < content-type: text/html; charset=ISO-8859-1
    13:29:11.252119 < p3p: CP="This is not a P3P policy! See g.co/p3phelp for more info."
    13:29:11.252160 < server: gws
    13:29:11.252198 < x-xss-protection: 1; mode=block
    13:29:11.252228 < x-frame-options: SAMEORIGIN
    13:29:11.252262 < set-cookie: 1P_JAR=2018-10-19-10; expires=Sun, 18-Nov-2018 10:29:11 GMT; path=/; domain=.google.com
    13:29:11.252297 < set-cookie: NID=141=pzXxp1jrJmLwFVl9bLMPFdGCtG8ySQKxB2rlDWgerrKJeXxfdmB1HhJ1UXzX-OaFQcnR1A9LKYxi__PWMigjMBQHmI3xkU53LI_TsYRbkMNJNdxs-caQQ7fEcDGE694S; expires=Sat, 20-Apr-2019 10:29:11 GMT; path=/; domain=.google.com; HttpOnly
    13:29:11.252336 < alt-svc: quic=":443"; ma=2592000; v="44,43,39,35"
    13:29:11.252368 < accept-ranges: none
    13:29:11.252408 < vary: Accept-Encoding
    13:29:11.252438 < 
    13:29:11.252473 { [5 bytes data]
    100 12215    0 12215    0     0   112k      0 --:--:-- --:--:-- --:--:--  112k
    13:29:11.255674 * Connection #0 to host www.google.com left intact
    
  • 116

    您可以根据此处的其他答案添加到.bashrc等的快捷方式:

    function perf {
      curl -o /dev/null -s -w "%{time_connect} + %{time_starttransfer} = %{time_total}\n" "$1"
    }
    

    用法:

    > perf stackoverflow.com
    0.521 + 0.686 = 1.290
    
  • 46

    这是答案:

    curl -X POST -d @file server:port -w %{time_connect}:%{time_starttransfer}:%{time_total}
    

    -w 一起使用的所有变量都可以在 man curl 中找到 .

  • 3

    Option 1. 要使用curl测量响应时间,请使用以下命令:

    curl -o /dev/null -s -w 'Total: %{time_total}\n'  https://www.google.com
    

    样本输出:

    Option 2. 要获取更多详细信息,请使用以下命令:

    curl -o /dev/null -s -w 'Connect: %{time_connect}\nStart Transfer: %{time_starttransfer}\nTotal: %{time_total}\n'  https://www.google.com
    

    样本输出:

    参考:Get response time with curl

  • 14

    来自这篇精彩的博文... https://blog.josephscott.org/2011/10/14/timing-details-with-curl/

    cURL支持格式化输出以获取请求的详细信息(请参阅the cURL manpage for details,在 -w, –write-out <format> 下) . 出于我们的目的,我们将仅关注所提供的时序细节 .

    • Create a new file, curl-format.txt, and paste in:
    time_namelookup:  %{time_namelookup}\n
           time_connect:  %{time_connect}\n
        time_appconnect:  %{time_appconnect}\n
       time_pretransfer:  %{time_pretransfer}\n
          time_redirect:  %{time_redirect}\n
     time_starttransfer:  %{time_starttransfer}\n
                        ----------\n
             time_total:  %{time_total}\n
    
    • Make a request:
    curl -w "@curl-format.txt" -o /dev/null -s "http://wordpress.com/"
    

    或者在Windows上,它是......

    curl -w "@curl-format.txt" -o NUL -s "http://wordpress.com/"
    

    这是做什么的:

    -w "@curl-format.txt" 告诉cURL使用我们的格式文件
    -o /dev/null 将请求的输出重定向到/ dev / null
    -s 告诉cURL不要显示进度表
    "http://wordpress.com/" 是我们要求的网址 . 如果您的URL具有"&"查询字符串参数,请使用引号

    这是你得到的:

    time_namelookup:  0.001
          time_connect:  0.037
       time_appconnect:  0.000
      time_pretransfer:  0.037
         time_redirect:  0.000
    time_starttransfer:  0.092
                       ----------
            time_total:  0.164
    

    制作Windows快捷方式(又名BAT文件)

    将此命令放在CURLTIME.BAT中(与curl.exe位于同一文件夹中)

    curl -w "@%~dp0curl-format.txt" -o NUL -s %*
    

    然后你可以简单地打电话......

    curltime wordpress.org
    
  • 3

    以下内容的灵感来自Simon 's answer. It' s自包含(不需要单独的格式文件),这使其非常适合包含在 .bashrc 中 .

    curl_time() {
        curl -so /dev/null -w "\
       namelookup:  %{time_namelookup}s\n\
          connect:  %{time_connect}s\n\
       appconnect:  %{time_appconnect}s\n\
      pretransfer:  %{time_pretransfer}s\n\
         redirect:  %{time_redirect}s\n\
    starttransfer:  %{time_starttransfer}s\n\
    -------------------------\n\
            total:  %{time_total}s\n" "$@"
    }
    

    此外,它应该适用于 curl 通常需要的所有参数,因为 "$@" 只是通过它们 . 例如,你可以这样做:

    curl_time -X POST -H "Content-Type: application/json" -d '{"key": "val"}' https://postman-echo.com/post
    

    输出:

    namelookup:  0,125000s
          connect:  0,250000s
       appconnect:  0,609000s
      pretransfer:  0,609000s
         redirect:  0,000000s
    starttransfer:  0,719000s
    -------------------------
            total:  0,719000s
    
  • 2

    如果您想分析或总结延迟,可以尝试使用apache bench:

    ab -n [number of samples] [url]
    

    例如:

    ab -n 100 http://www.google.com/
    

    它将显示:

    This is ApacheBench, Version 2.3 <$Revision: 1757674 $>
    Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
    Licensed to The Apache Software Foundation, http://www.apache.org/
    
    Benchmarking www.google.com (be patient).....done
    
    
    Server Software:        gws
    Server Hostname:        www.google.com
    Server Port:            80
    
    Document Path:          /
    Document Length:        12419 bytes
    
    Concurrency Level:      1
    Time taken for tests:   10.700 seconds
    Complete requests:      100
    Failed requests:        97
       (Connect: 0, Receive: 0, Length: 97, Exceptions: 0)
    Total transferred:      1331107 bytes
    HTML transferred:       1268293 bytes
    Requests per second:    9.35 [#/sec] (mean)
    Time per request:       107.004 [ms] (mean)
    Time per request:       107.004 [ms] (mean, across all concurrent requests)
    Transfer rate:          121.48 [Kbytes/sec] received
    
    Connection Times (ms)
                  min  mean[+/-sd] median   max
    Connect:       20   22   0.8     22      26
    Processing:    59   85 108.7     68     911
    Waiting:       59   85 108.7     67     910
    Total:         80  107 108.8     90     932
    
    Percentage of the requests served within a certain time (ms)
      50%     90
      66%     91
      75%     93
      80%     95
      90%    105
      95%    111
      98%    773
      99%    932
     100%    932 (longest request)
    
  • 66

    我做了一个友好的格式化程序来嗅探curl请求以帮助调试(参见使用注释) . 它包含您可以用易于阅读的格式写出的每个已知输出参数 .

    https://gist.github.com/manifestinteractive/ce8dec10dcb4725b8513

相关问题