Time for Memcache. Qcache off?

Seems like we constantly hover around 60% for Qcache hit rates. Based Qcache_hits / (Qcache_hits + Qcache_inserts)

MariaDB [(none)]> show status Like '%Qcache%';
+-------------------------+----------+
| Variable_name           | Value    |
+-------------------------+----------+
| Qcache_free_blocks      | 8618     |
| Qcache_free_memory      | 27146520 |
| Qcache_hits             | 14722398 |
| Qcache_inserts          | 8665581  |
| Qcache_lowmem_prunes    | 3151341  |
| Qcache_not_cached       | 708833   |
| Qcache_queries_in_cache | 25966    |
| Qcache_total_blocks     | 71756    |
+-------------------------+----------+
8 rows in set (0.03 sec)

The global wp_usermeta table in WordPress which is huge on a site like UBC Blogs is constantly being updated so the Qcache would constantly be invalidated. Wondering if we would be better off with it off? Does invalidation cost more than the savings… deep thoughts for a DBA…

Pretty sure if we committed to implementing Memcache for object cache we would would see gains.