On 28/11/2024 11:32, Cristian Prundeanu wrote: [...] > On 2024-11-26, Dietmar Eggemann wrote: > >> SUT kernel arm64 (mysql-8.4.0) >> (2) 6.12.0-rc4 -12.9% >> (3) 6.12.0-rc4 NO_PLACE_LAG +6.4% >> (4) v6.12-rc4 SCHED_BATCH +10.8% > > This is very interesting; our setups are close, yet I have not seen any > feature or policy combination that performs above the 6.5 CFS baseline. > I look forward to seeing your results with the repro when it's ready. > > Did you only use NO_PLACE_LAG or was it together with NO_RUN_TO_PARITY? Only NO_PLACE_LAG. > Was SCHED_BATCH used with the default feature set (all enabled)? Yes. > Which distro/version did you use for the SUT? The default, Ubuntu 24.04 Arm64 server. >> Maybe a difference in our test setup can explain the different test results: >> >> I use: >> >> HammerDB Load Generator <-> MySQL SUT >> 192 VCPUs <-> 16 VCPUs >> >> Virtual users: 256 >> Warehouse count: 64 >> 3 min rampup >> 10 min test run time >> performance data: NOPM (New Operations Per Minute) >> >> So I have 256 'connection' tasks running on the 16 SUT VCPUS. > > My setup: > > SUT - 16 vCPUs, 32 GB RAM > Loadgen - 64 vCPU, 128 GB RAM (anything large enough to not be a > bottleneck should work) > > Virtual users: 4 x vCPUs = 64 > Warehouses: 24 > Rampup: 5 min > Test runtime: 20 min x 10 times, each on 4 different SUT/Loadgen pairs > Value recorded: geometric_mean(NOPM) Looks like you have 4 times less 'connection' tasks on your 16 VCPUs. So much less concurrency/preemption ...
|