[wp-trac] [WordPress Trac] #57916: Explore and assess 6.2 server-side performance regressions
WordPress Trac
noreply at wordpress.org
Wed Mar 15 01:45:26 UTC 2023
#57916: Explore and assess 6.2 server-side performance regressions
----------------------------+--------------------------
Reporter: flixos90 | Owner: flixos90
Type: task (blessed) | Status: assigned
Priority: normal | Milestone: 6.2
Component: General | Version: trunk
Severity: normal | Resolution:
Keywords: | Focuses: performance
----------------------------+--------------------------
Comment (by joemcgill):
As a second data point here, I quickly ran some tests locally using wp-env
to spin up a site with the following config:
{{{
{
"config": {
"WP_DEBUG": false,
"WP_DEBUG_LOG": false,
"WP_DEBUG_DISPLAY": false,
"SCRIPT_DEBUG": false
}
}
}}}
I set loaded the Twenty Twenty-One theme and ran tests of 20 requests
using the Apache Bench tool (i.e., `ab`) for WP 6.1.1, 6.2-beta1, and
6.2-RC1, respectively, using WP CLI to update the site so the zip packages
would be applied. Here are the results that I got from these tests:
{{{
## 6.1.1
Document Path: /
Document Length: 62259 bytes
Concurrency Level: 1
Time taken for tests: 1.627 seconds
Complete requests: 20
Failed requests: 0
Total transferred: 1250420 bytes
HTML transferred: 1245180 bytes
Requests per second: 12.29 [#/sec] (mean)
Time per request: 81.367 [ms] (mean)
Time per request: 81.367 [ms] (mean, across all concurrent requests)
Transfer rate: 750.38 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 0
Processing: 52 81 89.5 56 458
Waiting: 30 56 84.6 34 415
Total: 52 81 89.5 57 459
Percentage of the requests served within a certain time (ms)
50% 57
66% 70
75% 70
80% 71
90% 98
95% 459
98% 459
99% 459
100% 459 (longest request)
## 6.2-beta1
Document Path: /
Document Length: 62433 bytes
Concurrency Level: 1
Time taken for tests: 1.448 seconds
Complete requests: 20
Failed requests: 0
Total transferred: 1253900 bytes
HTML transferred: 1248660 bytes
Requests per second: 13.81 [#/sec] (mean)
Time per request: 72.390 [ms] (mean)
Time per request: 72.390 [ms] (mean, across all concurrent requests)
Transfer rate: 845.77 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 0
Processing: 44 72 101.5 47 503
Waiting: 26 53 98.5 29 471
Total: 44 72 101.6 47 503
Percentage of the requests served within a certain time (ms)
50% 47
66% 51
75% 54
80% 56
90% 70
95% 503
98% 503
99% 503
100% 503 (longest request)
## 6.2-RC1
Document Path: /
Document Length: 62613 bytes
Concurrency Level: 1
Time taken for tests: 1.289 seconds
Complete requests: 20
Failed requests: 0
Total transferred: 1257500 bytes
HTML transferred: 1252260 bytes
Requests per second: 15.51 [#/sec] (mean)
Time per request: 64.475 [ms] (mean)
Time per request: 64.475 [ms] (mean, across all concurrent requests)
Transfer rate: 952.33 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 0
Processing: 43 64 69.6 49 360
Waiting: 26 45 67.0 29 329
Total: 43 64 69.6 49 360
Percentage of the requests served within a certain time (ms)
50% 49
66% 51
75% 52
80% 54
90% 56
95% 360
98% 360
99% 360
100% 360 (longest request)
}}}
I'd like to retry this process using the same server timing method that
@flixos90 has reported, but from this initial simple set of checks, it
would seem to confirm what our automated performance workflows have been
saying, which is that Twenty Twenty One is loading faster on WP 6.2 than
on WP 6.1 in a default configuration.
@flixos90 could you add more detail about the method you're using to get
the results you're seeing so that I and others can try to reproduce?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/57916#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list