6 ms·

I have absolutely no idea regarding cpus but would this also speed up database caching?

• stingraycharles 3y ago
  Generally memory has different access speeds. In order for a CPU to actually perform operations on the data, it needs to be loaded into the memory closest to / within the CPU. L1 cache is the fastest (and closest to the CPU), but there’s very few of it. There’s also L2, L3 and L4, each being slightly slower but larger than the previous one. VCache is a new kind of mechanism where the caching layer is placed vertically “on top” of the CPU. This unlocks new possibilities, and possibly more cache available at lower access times, but there are some technical challenges to make it work. It will enable your database to perform computations faster, as more data can be stored closer to the CPU.
  • loeg 3y ago
    VCache is more or less just a big L3 cache, with some quirks due to the way it is implemented. It's slightly slower than on-die L3 (~10%); on the bigger chips, it can only be accessed from a single CCD, etc.
• justsomehnguy 3y ago
  Not if you modus operandi is to SELECT * FROM t1 WHERE (SELECT * FROM t1 WHERE (SELECT * FROM t1.... EDIT: for whose who downvoted: https://news.ycombinator.com/item?id=32720856 https://news.ycombinator.com/item?id=32720856
  • trollied 3y ago
    ... then stream the entire resultset to the server and do the filtering in software. Drives me mad!
• loeg 3y ago
  If your working set is between 32 and 96 MB, it can make a big difference. This is probably not what most people mean when they talk about database caching, though.
• jackmott 3y ago
  [dead]
• ilyt 3y ago
  It will generally speed up things that do a bunch of operation of smallish set of data Databases usually do a few (say a compare, maybe bit spicy compare) on big set of data