4 ms·

Thanks - this is what's worrying me: the result of patching seems to be all over the map, and it's somewhat hard to predict. My biggest worry is SQL Server, so

• Abishek_Muthian 9y ago
  Judging from our MongoDB instance, I'm optimistic that your SQL server wouldn't face much impact either. Even Redhat tests put the risk at modest. But for something like Redis, the case could be different. If you are on a cloud provider, do check that automatic update is not scheduled; if so it's better to update manually to follow up with mitigation if necessary.
  • dijit 9y ago
    This is almost entirely subjective and workload dependent. We know that the biggest performance factor in both of these patches (spectre, meltdown) is the kernel boundary. So saying something along the lines of "Redis is more affected than Mongo" is.. odd. MongoDB (I HOPE) will save files more frequently than redis, since redis is primarily in in-memory DB with some lazy IO access (depending on configuration). So if you have a lot of small network calls to redis (which, is a kernel boundary event.) then it will be more impacted than a mongodb which takes only a few very large requests. My gut is that the opposite would be true for the same workloads on both, MongoDB needs its files to return data, redis doesn't. Even the vfs-cache is in kernel "space", so if your entire data sat in vfs cache it wouldn't help. But that's my gut, and your exact usage may not mirror the 1:1 of this scenario.