Want to subscribe to topics you're interested in?
Become a Member

Beta Branch centmin.sh menu 22 add WPCLI_CE_QUERYSTRING_INCLUDED='n' in 123.09beta01

Discussion in 'Centmin Mod Github Commits' started by eva2000, Sep 1, 2020.

  1. eva2000

    eva2000 Administrator Staff Member

    45,201
    10,279
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +15,933
    Local Time:
    9:16 PM
    Nginx 1.19.x
    MariaDB 5.5/10.x
    centmin.sh menu 22 add WPCLI_CE_QUERYSTRING_INCLUDED='n' in 123.09beta01

    For centmin.sh menu option 22, Cache Enabler wordpress installs add optional persistent config file variable WPCLI_CE_QUERYSTRING_INCLUDED='n' which controls where select query string values are included in Cache Enabler's guest full HTML page caching routine which uses advanced caching at Nginx level bypassing PHP-FPM completely Wordpress - Ensuring urls with utm params, fbclid, adwords params are served from cache. Disabled by default, but can be enabled by setting WPCLI_CE_QUERYSTRING_INCLUDED='y' in persistent config file /etc/centminmod/custom_config.inc prior to running centmin.sh menu option 22 wordpress installer.

    The select query strings for cache inclusion are setup via a regular expression for
    Code (Text):
    /^fbclid|utm_(source|medium|campaign|term|content|expid)|gclid|fb_(action_ids|action_types|source)|age-verified|ao_noptimize|usqp|cn-reloaded|_ga|_ke$/

    which can be modified or removed via Cache Enabler WP Admin settings later on.

    Existing Centmin Mod wordpress cache enabler installs need to do it manually as outlined at Wordpress - Ensuring urls with utm params, fbclid, adwords params are served from cache

    Continue reading...

    123.09beta01 branch
     
    Last edited: Sep 5, 2020
  2. eva2000

    eva2000 Administrator Staff Member

    45,201
    10,279
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +15,933
    Local Time:
    9:16 PM
    Nginx 1.19.x
    MariaDB 5.5/10.x
    Example for ?fbclid query string cache inclusion with centmin.sh menu option 22 Wordpress installation with Cache Enabler advanced caching - guest full HTML page caching at Nginx level (complete bypass PHP-FPM instead of normal Cache Enabler PHP based caching)
    Code (Text):
    --------------------------------------------------------
         Centmin Mod Menu 123.09beta01 centminmod.com
    --------------------------------------------------------
    1).  Centmin Install
    2).  Add Nginx vhost domain
    3).  NSD setup domain name DNS
    4).  Nginx Upgrade / Downgrade
    5).  PHP Upgrade / Downgrade
    6).  XCache Re-install
    7).  APC Cache Re-install
    8).  XCache Install
    9).  APC Cache Install
    10). Memcached Server Re-install
    11). MariaDB MySQL Upgrade & Management
    12). Zend OpCache Install/Re-install
    13). Install/Reinstall Redis PHP Extension
    14). SELinux disable
    15). Install/Reinstall ImagicK PHP Extension
    16). Change SSHD Port Number
    17). Multi-thread compression: zstd,pigz,pbzip2,lbzip2
    18). Suhosin PHP Extension install
    19). Install FFMPEG and FFMPEG PHP Extension
    20). NSD Install/Re-Install
    21). Data Transfer (TBA)
    22). Add Wordpress Nginx vhost + Cache Plugin
    23). Update Centmin Mod Code Base
    24). Exit
    --------------------------------------------------------
    Enter option [ 1 - 24 ] 22
    

    Code (Text):
    Default is to install KeyCDN WP Cache Enabler Plugin
    as it's more stable and reliable than WP Super Cache.
    Redis cache may have issues with caching due to long 6hr cache TTL
    You can select which caching method to use below:
    
    --------------------------------------------------------
            Wordpress Caching      
    --------------------------------------------------------
    1) KeyCDN Cache Enabler
    2) Redis Nginx Level Caching
    3) Wordpress Super Cache
    --------------------------------------------------------
    Enter option [ 1 - 3 ]
    you selected option 1 (KeyCDN Cache Enabler) [wpscache=n]
    

    Code (Text):
    curl -sk "https://cache-enabler2.domain.com/?fbclid" | tail -2              
    <!-- Cache Enabler by KeyCDN @ 31.08.2020 21:21:07 (https html) -->
    

    at 50 user concurrency
    Code (Text):
    wrk-cmm -t4 -c50 -d20s --latency --breakout https://cache-enabler2.domain.com/?fbclid
    Running 20s test @ https://cache-enabler2.domain.com/?fbclid
      4 threads and 50 connections
      Thread Stats   Avg      Stdev     Max   +/- Stdev
        Latency     1.90ms    2.31ms  24.96ms   88.75%
        Connect     5.41ms    3.30ms  18.46ms   54.03%
        TTFB        1.42ms    2.17ms  23.91ms   88.82%
        TTLB      460.12us  594.82us  20.43ms   93.99%
        Req/Sec     8.64k     2.03k   14.93k    69.75%
      Latency Distribution
         50%    1.20ms
         75%    2.35ms
         90%    4.68ms
         95%    7.31ms
         99%   10.95ms
      688839 requests in 20.05s, 8.44GB read
    Requests/sec:  34353.00
    Transfer/sec:    431.23MB
    

    at 250 user concurrency
    Code (Text):
    wrk-cmm -t4 -c250 -d20s --latency --breakout https://cache-enabler2.domain.com/?fbclid
    Running 20s test @ https://cache-enabler2.domain.com/?fbclid
      4 threads and 250 connections
      Thread Stats   Avg      Stdev     Max   +/- Stdev
        Latency    11.81ms    5.83ms  63.32ms   65.44%
        Connect    29.69ms   12.38ms  63.18ms   64.64%
        TTFB        7.27ms    4.75ms  58.30ms   66.95%
        TTLB        4.49ms    2.32ms  32.79ms   76.74%
        Req/Sec     5.16k   558.73     6.69k    71.75%
      Latency Distribution
         50%   13.28ms
         75%   15.19ms
         90%   17.52ms
         95%   19.72ms
         99%   27.97ms
      411754 requests in 20.09s, 9.05GB read
    Requests/sec:  20498.20
    Transfer/sec:    461.56MB
    

    at 500 user concurrency
    Code (Text):
    wrk-cmm -t4 -c500 -d20s --latency --breakout https://cache-enabler2.domain.com/?fbclid
    Running 20s test @ https://cache-enabler2.domain.com/?fbclid
      4 threads and 500 connections
      Thread Stats   Avg      Stdev     Max   +/- Stdev
        Latency    24.09ms    9.91ms 149.90ms   70.97%
        Connect    74.37ms   36.67ms 169.90ms   65.67%
        TTFB        9.74ms    8.11ms 128.70ms   74.50%
        TTLB       14.32ms    5.90ms  43.82ms   64.14%
        Req/Sec     5.04k   622.31     7.26k    72.92%
      Latency Distribution
         50%   23.50ms
         75%   29.90ms
         90%   35.87ms
         95%   39.71ms
         99%   48.03ms
      400188 requests in 20.09s, 8.80GB read
    Requests/sec:  19924.56
    Transfer/sec:    448.78MB
    

    at 1000 user concurrency
    Code (Text):
    wrk-cmm -t4 -c1000 -d20s --latency --breakout https://cache-enabler2.domain.com/?fbclid
    Running 20s test @ https://cache-enabler2.domain.com/?fbclid
      4 threads and 1000 connections
      Thread Stats   Avg      Stdev     Max   +/- Stdev
        Latency    50.62ms   11.76ms 255.06ms   77.43%
        Connect   148.64ms   62.92ms 295.34ms   60.05%
        TTFB       11.82ms    9.40ms 205.51ms   80.42%
        TTLB       38.78ms    7.84ms  73.57ms   68.35%
        Req/Sec     4.76k   641.98     6.56k    72.87%
      Latency Distribution
         50%   49.94ms
         75%   56.53ms
         90%   62.97ms
         95%   67.49ms
         99%   77.39ms
      375287 requests in 20.09s, 8.26GB read
    Requests/sec:  18683.82
    Transfer/sec:    421.00MB
    

    at 2000 user concurrency
    Code (Text):
    wrk-cmm -t4 -c2000 -d20s --latency --breakout https://cache-enabler2.domain.com/?fbclid
    Running 20s test @ https://cache-enabler2.domain.com/?fbclid
      4 threads and 2000 connections
      Thread Stats   Avg      Stdev     Max   +/- Stdev
        Latency   107.25ms   19.35ms 472.03ms   84.14%
        Connect   294.46ms  111.55ms 546.68ms   62.35%
        TTFB       15.98ms   16.38ms 374.69ms   97.02%
        TTLB       91.15ms   11.56ms 141.23ms   68.80%
        Req/Sec     4.48k   646.71     6.25k    75.80%
      Latency Distribution
         50%  105.64ms
         75%  114.94ms
         90%  124.21ms
         95%  130.72ms
         99%  150.17ms
      348571 requests in 20.08s, 7.68GB read
    Requests/sec:  17362.38
    Transfer/sec:    391.91MB
    

    at 5000 user concurrency
    Code (Text):
    wrk-cmm -t4 -c5000 -d20s --latency --breakout https://cache-enabler2.domain.com/?fbclid
    Running 20s test @ https://cache-enabler2.domain.com/?fbclid
      4 threads and 5000 connections
      Thread Stats   Avg      Stdev     Max   +/- Stdev
        Latency   291.89ms   57.54ms   1.11s    96.38%
        Connect   727.83ms  250.64ms   1.30s    62.96%
        TTFB       35.27ms   58.71ms 829.15ms   97.69%
        TTLB      255.91ms   20.30ms 326.60ms   72.91%
        Req/Sec     4.15k     1.36k    9.36k    78.04%
      Latency Distribution
         50%  284.78ms
         75%  300.22ms
         90%  316.00ms
         95%  329.37ms
         99%  585.72ms
      310084 requests in 20.08s, 6.86GB read
    Requests/sec:  15445.19
    Transfer/sec:    350.10MB
    

    at 8000 user concurrency
    Code (Text):
    wrk-cmm -t4 -c8000 -d20s --latency --breakout https://cache-enabler2.domain.com/?fbclid
    Running 20s test @ https://cache-enabler2.domain.com/?fbclid
      4 threads and 8000 connections
      Thread Stats   Avg      Stdev     Max   +/- Stdev
        Latency   471.60ms  107.52ms   1.51s    94.76%
        Connect     1.13s   371.20ms   1.93s    61.77%
        TTFB       61.30ms  118.71ms   1.22s    95.98%
        TTLB      408.73ms   48.79ms 505.90ms   86.50%
        Req/Sec     4.11k     1.21k    8.68k    73.09%
      Latency Distribution
         50%  455.92ms
         75%  481.49ms
         90%  508.53ms
         95%  542.96ms
         99%    1.06s
      297178 requests in 20.04s, 6.61GB read
    Requests/sec:  14827.88
    Transfer/sec:    337.95MB
    

    and with h2load HTTP/2 load tester

    h2load HTTP/2 HTTPS with 50 concurrent users and 100,000 requests
    Code (Text):
    h2load -t4 -c50 -n100000 -m60 https://cache-enabler2.domain.com/?fbclid
    starting benchmark...
    spawning thread #0: 13 total client(s). 25000 total requests
    spawning thread #1: 13 total client(s). 25000 total requests
    spawning thread #2: 12 total client(s). 25000 total requests
    spawning thread #3: 12 total client(s). 25000 total requests
    TLS Protocol: TLSv1.2
    Cipher: ECDHE-ECDSA-AES128-GCM-SHA256
    Server Temp Key: ECDH P-256 256 bits
    Application protocol: h2
    progress: 10% done
    progress: 20% done
    progress: 30% done
    progress: 40% done
    progress: 50% done
    progress: 60% done
    progress: 70% done
    progress: 80% done
    progress: 90% done
    progress: 100% done
    finished in 2.74s, 36470.98 req/s, 807.67MB/s
    requests: 100000 total, 100000 started, 100000 done, 100000 succeeded, 0 failed, 0 errored, 0 timeout
    status codes: 100000 2xx, 0 3xx, 0 4xx, 0 5xx
    traffic: 2.16GB (2322116797) total, 1.44MB (1514347) headers (space savings 95.65%), 2.16GB (2317000000) data
                         min         max         mean         sd        +/- sd
    time for request:     2.49ms    132.76ms     74.44ms     16.61ms    68.00%
    time for connect:     9.17ms    130.91ms     27.09ms     26.50ms    88.00%
    time to 1st byte:    11.62ms    181.67ms     77.04ms     41.64ms    66.00%
    req/s           :     701.41      866.30      763.64       65.30    76.00%
    

    h2load HTTP/2 HTTPS with 500 concurrent users and 100,000 requests
    Code (Text):
    h2load -t4 -c500 -n100000 -m60 https://cache-enabler2.domain.com/?fbclid
    starting benchmark...
    spawning thread #0: 125 total client(s). 25000 total requests
    spawning thread #1: 125 total client(s). 25000 total requests
    spawning thread #2: 125 total client(s). 25000 total requests
    spawning thread #3: 125 total client(s). 25000 total requests
    TLS Protocol: TLSv1.2
    Cipher: ECDHE-ECDSA-AES128-GCM-SHA256
    Server Temp Key: ECDH P-256 256 bits
    Application protocol: h2
    progress: 10% done
    progress: 20% done
    progress: 30% done
    progress: 40% done
    progress: 50% done
    progress: 60% done
    progress: 70% done
    progress: 80% done
    progress: 90% done
    progress: 100% done
    finished in 3.22s, 31018.76 req/s, 686.97MB/s
    requests: 100000 total, 100000 started, 100000 done, 100000 succeeded, 0 failed, 0 errored, 0 timeout
    status codes: 100000 2xx, 0 3xx, 0 4xx, 0 5xx
    traffic: 2.16GB (2322269971) total, 1.57MB (1645471) headers (space savings 95.27%), 2.16GB (2317000000) data
                         min         max         mean         sd        +/- sd
    time for request:    35.99ms    220.72ms    145.62ms     22.15ms    80.09%
    time for connect:    16.90ms    303.35ms    185.06ms     83.47ms    55.00%
    time to 1st byte:    73.93ms    518.16ms    318.11ms    105.60ms    59.80%
    req/s           :      62.08       70.00       64.38        1.33    60.40%
    

    h2load HTTP/2 HTTPS with 1000 concurrent users and 100,000 requests
    Code (Text):
    h2load -t4 -c1000 -n100000 -m60 https://cache-enabler2.domain.com/?fbclid
    starting benchmark...
    spawning thread #0: 250 total client(s). 25000 total requests
    spawning thread #1: 250 total client(s). 25000 total requests
    spawning thread #2: 250 total client(s). 25000 total requests
    spawning thread #3: 250 total client(s). 25000 total requests
    TLS Protocol: TLSv1.2
    Cipher: ECDHE-ECDSA-AES128-GCM-SHA256
    Server Temp Key: ECDH P-256 256 bits
    Application protocol: h2
    progress: 10% done
    progress: 20% done
    progress: 30% done
    progress: 40% done
    progress: 50% done
    progress: 60% done
    progress: 70% done
    progress: 80% done
    progress: 90% done
    progress: 100% done
    finished in 3.41s, 29336.46 req/s, 649.76MB/s
    requests: 100000 total, 100000 started, 100000 done, 100000 succeeded, 0 failed, 0 errored, 0 timeout
    status codes: 100000 2xx, 0 3xx, 0 4xx, 0 5xx
    traffic: 2.16GB (2322437849) total, 1.71MB (1788849) headers (space savings 94.86%), 2.16GB (2317000000) data
                         min         max         mean         sd        +/- sd
    time for request:    39.45ms    417.41ms    285.48ms     52.79ms    84.33%
    time for connect:    20.07ms    893.38ms    320.83ms    186.55ms    71.70%
    time to 1st byte:   156.65ms       1.18s    587.64ms    225.16ms    67.70%
    req/s           :      29.55       36.51       31.42        1.09    74.70%
    

    h2load HTTP/2 HTTPS with 2000 concurrent users and 100,000 requests
    Code (Text):
    h2load -t4 -c2000 -n100000 -m60 https://cache-enabler2.domain.com/?fbclid
    starting benchmark...
    spawning thread #0: 500 total client(s). 25000 total requests
    spawning thread #1: 500 total client(s). 25000 total requests
    spawning thread #2: 500 total client(s). 25000 total requests
    spawning thread #3: 500 total client(s). 25000 total requests
    TLS Protocol: TLSv1.2
    Cipher: ECDHE-ECDSA-AES128-GCM-SHA256
    Server Temp Key: ECDH P-256 256 bits
    Application protocol: h2
    progress: 10% done
    progress: 20% done
    progress: 30% done
    progress: 40% done
    progress: 50% done
    progress: 60% done
    progress: 70% done
    progress: 80% done
    progress: 90% done
    progress: 100% done
    finished in 3.74s, 26771.29 req/s, 593.02MB/s
    requests: 100000 total, 100000 started, 100000 done, 100000 succeeded, 0 failed, 0 errored, 0 timeout
    status codes: 100000 2xx, 0 3xx, 0 4xx, 0 5xx
    traffic: 2.16GB (2322736276) total, 1.94MB (2038276) headers (space savings 94.14%), 2.16GB (2317000000) data
                         min         max         mean         sd        +/- sd
    time for request:    33.86ms       1.01s    579.41ms    139.05ms    75.90%
    time for connect:    34.30ms       1.40s    534.88ms    267.63ms    88.75%
    time to 1st byte:   386.74ms       2.07s       1.08s    365.92ms    77.20%
    req/s           :      13.51       18.82       14.55        0.58    61.55%
    

    h2load HTTP/2 HTTPS with 5000 concurrent users and 100,000 requests
    Code (Text):
    h2load -t4 -c5000 -n100000 -m60 https://cache-enabler2.domain.com/?fbclid
    starting benchmark...
    spawning thread #0: 1250 total client(s). 25000 total requests
    spawning thread #1: 1250 total client(s). 25000 total requests
    spawning thread #2: 1250 total client(s). 25000 total requests
    spawning thread #3: 1250 total client(s). 25000 total requests
    TLS Protocol: TLSv1.2
    Cipher: ECDHE-ECDSA-AES128-GCM-SHA256
    Server Temp Key: ECDH P-256 256 bits
    Application protocol: h2
    progress: 10% done
    progress: 20% done
    progress: 30% done
    progress: 40% done
    progress: 50% done
    progress: 60% done
    progress: 70% done
    progress: 80% done
    progress: 90% done
    progress: 100% done
    finished in 4.90s, 20411.62 req/s, 452.31MB/s
    requests: 100000 total, 100000 started, 100000 done, 100000 succeeded, 0 failed, 0 errored, 0 timeout
    status codes: 100000 2xx, 0 3xx, 0 4xx, 0 5xx
    traffic: 2.16GB (2323574195) total, 2.60MB (2729195) headers (space savings 92.16%), 2.16GB (2317000000) data
                         min         max         mean         sd        +/- sd
    time for request:    79.53ms       2.55s       1.39s    538.43ms    66.05%
    time for connect:    87.70ms       3.44s       1.32s    624.32ms    90.72%
    time to 1st byte:   980.61ms       4.73s       2.53s    846.72ms    75.06%
    req/s           :       4.16       14.25        4.92        0.51    68.80%
    

    h2load HTTP/2 HTTPS with 10,000 concurrent users and 100,000 requests
    Code (Text):
    h2load -t4 -c10000 -n100000 -m60 https://cache-enabler2.domain.com/?fbclid
    starting benchmark...
    spawning thread #0: 2500 total client(s). 25000 total requests
    spawning thread #1: 2500 total client(s). 25000 total requests
    spawning thread #2: 2500 total client(s). 25000 total requests
    spawning thread #3: 2500 total client(s). 25000 total requests
    TLS Protocol: TLSv1.2
    Cipher: ECDHE-ECDSA-AES128-GCM-SHA256
    Server Temp Key: ECDH P-256 256 bits
    Application protocol: h2
    progress: 10% done
    progress: 20% done
    progress: 30% done
    progress: 40% done
    progress: 50% done
    progress: 60% done
    progress: 70% done
    progress: 80% done
    progress: 90% done
    progress: 100% done
    finished in 6.16s, 16224.14 req/s, 359.71MB/s
    requests: 100000 total, 100000 started, 100000 done, 100000 succeeded, 0 failed, 0 errored, 0 timeout
    status codes: 100000 2xx, 0 3xx, 0 4xx, 0 5xx
    traffic: 2.17GB (2324820000) total, 3.56MB (3730000) headers (space savings 89.28%), 2.16GB (2317000000) data
                         min         max         mean         sd        +/- sd
    time for request:   342.62ms       3.12s       1.82s    716.09ms    60.58%
    time for connect:   135.12ms       3.23s       2.64s    703.03ms    86.39%
    time to 1st byte:   813.67ms       6.10s       4.46s       1.11s    58.58%
    req/s           :       1.64       12.27        2.42        0.79    84.33%
    

    h2load HTTP/2 HTTPS with 15,000 concurrent users and 100,000 requests
    Code (Text):
    h2load -t4 -c15000 -n100000 -m60 https://cache-enabler2.domain.com/?fbclid
    starting benchmark...
    spawning thread #0: 3750 total client(s). 25000 total requests
    spawning thread #1: 3750 total client(s). 25000 total requests
    spawning thread #2: 3750 total client(s). 25000 total requests
    spawning thread #3: 3750 total client(s). 25000 total requests
    TLS Protocol: TLSv1.2
    Cipher: ECDHE-ECDSA-AES128-GCM-SHA256
    Server Temp Key: ECDH P-256 256 bits
    Application protocol: h2
    progress: 10% done
    progress: 20% done
    progress: 30% done
    progress: 40% done
    progress: 50% done
    progress: 60% done
    progress: 70% done
    progress: 80% done
    progress: 90% done
    progress: 100% done
    finished in 7.93s, 12602.60 req/s, 279.58MB/s
    requests: 100000 total, 100000 started, 100000 done, 100000 succeeded, 0 failed, 0 errored, 0 timeout
    status codes: 100000 2xx, 0 3xx, 0 4xx, 0 5xx
    traffic: 2.17GB (2326180000) total, 4.62MB (4845000) headers (space savings 86.08%), 2.16GB (2317000000) data
                         min         max         mean         sd        +/- sd
    time for request:    96.69ms       3.97s       2.45s       1.11s    70.87%
    time for connect:   201.92ms       7.13s       3.81s       1.71s    75.69%
    time to 1st byte:      2.43s       7.74s       6.19s    848.49ms    60.79%
    req/s           :       0.78        2.47        1.10        0.19    61.03%
    

    h2load HTTP/2 HTTPS with 20,000 concurrent users and 100,000 requests
    Code (Text):
    h2load -t4 -c20000 -n100000 -m60 https://cache-enabler2.domain.com/?fbclid
    starting benchmark...
    spawning thread #0: 5000 total client(s). 25000 total requests
    spawning thread #1: 5000 total client(s). 25000 total requests
    spawning thread #2: 5000 total client(s). 25000 total requests
    spawning thread #3: 5000 total client(s). 25000 total requests
    TLS Protocol: TLSv1.2
    Cipher: ECDHE-ECDSA-AES128-GCM-SHA256
    Server Temp Key: ECDH P-256 256 bits
    Application protocol: h2
    progress: 10% done
    progress: 20% done
    progress: 30% done
    progress: 40% done
    progress: 50% done
    progress: 60% done
    progress: 70% done
    progress: 80% done
    progress: 90% done
    progress: 100% done
    finished in 9.45s, 10579.86 req/s, 234.84MB/s
    requests: 100000 total, 100000 started, 100000 done, 100000 succeeded, 0 failed, 0 errored, 0 timeout
    status codes: 100000 2xx, 0 3xx, 0 4xx, 0 5xx
    traffic: 2.17GB (2327540000) total, 5.68MB (5960000) headers (space savings 82.87%), 2.16GB (2317000000) data
                         min         max         mean         sd        +/- sd
    time for request:   526.06ms       3.78s       2.28s    846.49ms    57.11%
    time for connect:   732.84ms       6.75s       5.00s       1.81s    68.16%
    time to 1st byte:      2.10s       9.33s       7.28s       1.34s    49.15%
    req/s           :       0.54        2.38        0.71        0.14    56.46%
    

    h2load HTTP/2 HTTPS with 25,000 concurrent users and 100,000 requests
    Code (Text):
    h2load -t4 -c25000 -n100000 -m60 https://cache-enabler2.domain.com/?fbclid 
    starting benchmark...
    spawning thread #0: 6250 total client(s). 25000 total requests
    spawning thread #1: 6250 total client(s). 25000 total requests
    spawning thread #2: 6250 total client(s). 25000 total requests
    spawning thread #3: 6250 total client(s). 25000 total requests
    TLS Protocol: TLSv1.2
    Cipher: ECDHE-ECDSA-AES128-GCM-SHA256
    Server Temp Key: ECDH P-256 256 bits
    Application protocol: h2
    progress: 10% done
    progress: 20% done
    progress: 30% done
    progress: 40% done
    progress: 50% done
    progress: 60% done
    progress: 70% done
    progress: 80% done
    progress: 90% done
    progress: 100% done
    finished in 10.89s, 9182.13 req/s, 203.94MB/s
    requests: 100000 total, 100000 started, 100000 done, 100000 succeeded, 0 failed, 0 errored, 0 timeout
    status codes: 100000 2xx, 0 3xx, 0 4xx, 0 5xx
    traffic: 2.17GB (2328900000) total, 6.75MB (7075000) headers (space savings 79.67%), 2.16GB (2317000000) data
                         min         max         mean         sd        +/- sd
    time for request:   807.17ms       4.19s       2.69s       1.02s    52.84%
    time for connect:   864.58ms       6.87s       6.02s       1.05s    94.52%
    time to 1st byte:      1.72s      10.85s       8.71s       1.42s    59.54%
    req/s           :       0.37        2.32        0.47        0.09    70.12%
    


    Note these tests were with Centmin Mod 123.09beta01's optional Nginx HTTP/2 full HPACK encoding patch and Dynamic TLS record size patches enabled in persistent config file /etc/centminmod/custom_config.inc. Hence, why you see h2load results with such high header space savings percentage in 90+% instead of Nginx's usual 20-30% header space savings.
    Code (Text):
    NGINX_HPACK='y'
    NGINX_DYNAMICTLS='y'
    
     
  3. ahmed

    ahmed Active Member

    350
    48
    28
    Feb 21, 2017
    Ratings:
    +61
    Local Time:
    1:16 PM
    Great effort, killing the need for varnish, what about the old wordpress setup, do I need to do anything apart from the persistent config?
     
  4. eva2000

    eva2000 Administrator Staff Member

    45,201
    10,279
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +15,933
    Local Time:
    9:16 PM
    Nginx 1.19.x
    MariaDB 5.5/10.x
  5. eva2000

    eva2000 Administrator Staff Member

    45,201
    10,279
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +15,933
    Local Time:
    9:16 PM
    Nginx 1.19.x
    MariaDB 5.5/10.x
    found a bug in the setup for WPCLI_CE_QUERYSTRING_INCLUDED='y' in that generated /usr/local/nginx/conf/wpcacheenabler_map.conf

    it had improperly escaped double quotes like
    Code (Text):
    map $args $q_ignorearg {
      default                 0;
      \"~*fbclid\"            1;
      \"~*gclid\"             1;
      \"~*utm\"               1;
      \"~*fb_action_ids\"     1;
      \"~*fb_action_types\"   1;
      \"~*fb_source\"         1;
      \"~*age-verified\"      1;
      \"~*ao_noptimize\"      1;
      \"~*usqp\"              1;
      \"~*cn-reloaded\"       1;
      \"~*_ga\"               1;
      \"~*_ke\"               1;
    }

    when it should be like
    Code (Text):
    map $args $q_ignorearg {
      default                 0;
      "~*fbclid"            1;
      "~*gclid"             1;
      "~*utm"               1;
      "~*fb_action_ids"     1;
      "~*fb_action_types"   1;
      "~*fb_source"         1;
      "~*age-verified"      1;
      "~*ao_noptimize"      1;
      "~*usqp"              1;
      "~*cn-reloaded"       1;
      "~*_ga"               1;
      "~*_ke"               1;
    }

    I'll try to auto correct that in next update but for now double check your /usr/local/nginx/conf/wpcacheenabler_map.conf include file