[wp-trac] [WordPress Trac] #60011: 6.4.1 seems to deliver poor external cache performance compared with 6.3.2

[WordPress Trac]

#60011: 6.4.1 seems to deliver poor external cache performance compared with 6.3.2
--------------------------+------------------------------
 Reporter:  bjornha       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Cache API     |     Version:  6.4
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  performance
--------------------------+------------------------------

Comment (by bjornha):

 The output from wp regis debug is quite limited, only aggregating values,
 not specifying actual keys.
 What I do see as difference when calling the 6.4.1 environment is that it
 does not seem to try to mitigate misses.
 In 6.4.1 I consistently get the same figures for all calls and there are
 no “sets” being reported at all.
 For instance, in 6.4.1 this:
 wp redis debug --url=https://testwpadmin.pro4u.se/avtalslista
 leads to this:
 array (
   'cache_hits' => 21486,
   'cache_misses' => 41,
   'redis_calls' =>
   array (
     'get' => 98,
     'mget' => 7,
   ),
 )
 No change ever here.

 In 6.3.2 I see this behavior.
 After first call:
 array (
   'cache_hits' => 37023,
   'cache_misses' => 24,
   'redis_calls' =>
   array (
     'get' => 76,
     'mget' => 7,
     'set' => 3,
   ),
 )
 After second call
 array (
   'cache_hits' => 37030,
   'cache_misses' => 21,
   'redis_calls' =>
   array (
     'get' => 76,
     'mget' => 7,
   ),
 )
 Here you can see that cache misses goes down with the amount of “sets”
 that was done in the previous call.
 But I don’t know how useful this is as it does not specify actual actions
 towards Redis.

 /bjørn h

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/60011#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform