News for hackers. Stuff that matters.
Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand... by diziet on Thursday March 31, 2016 @03:52PM (#11400101)
What's very interesting is that in most cases with either modern PCIe-connection based SSDs or multiple SSD drives, database performance has become CPU limited once again in operations that require multiple transactions. These chips surely help with the higher processor counts.
Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand... by vardump on Thursday March 31, 2016 @04:13PM (#11400252)
Need to still wait until Skylake for CLWB and PCOMMIT x86 NVM aka "SSD-instructions".

http://danluu.com/clwb-pcommit/

Maybe we need even more cores soon...

Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand... by jakub_h on Thursday March 31, 2016 @08:08PM (#11401585)
Wouldn't SSDs - and even better system-bus-connected storage contraptions - also drive the use of different algorithms? I can see how merely cutting the disk latencies by two (or more) orders of magnitude leaves you starved for computational resources, but you don't have to do many things at that point. Data packing is different (could be even CPU matched now?), access patterns can be more random, etc.
Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand... by dietrichepp on Thursday March 31, 2016 @09:55PM (#11402035)
That's an interesting question, but I expect many of the algorithms will stay the same. Think of a computer as having a multi-level cache: network -> disk -> ram -> L2 cache -> L1 cache -> register, each one smaller than the last. We're seeing a big change in disk latency, but that's only one part of the chain. For example, we're still going to be optimizing data structures to fit in L1 cache lines.
Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand... by njohnson41 on Thursday March 31, 2016 @11:03PM (#11402267)
Interestingly, that may be the new ordering if the disks are SSDs, but the typical seek latency on a spinning disk (~5 ms) is definitely higher than the latency to read data from another machine's memory across ethernet (a few hundred us), and even the bandwidths are comparable (~150 MB/s).

So, now it has jumped from (disk -> network -> memory -> ...) to (network -> disk -> memory -> ...), which is a big change.

Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand... by vardump on Friday April 01, 2016 @06:17AM (#11403842)
> network -> disk -> ram -> L2 cache -> L1 cache -> register

It's more and more like network/disk -> L3 cache -> L2 cache. DRAM is pretty slow.

Because PCIe controller is anyways on the same chip as L3 cache, there's no reason to send the data on a long trip to DRAM and back. Until, of course, when the cache line gets evicted for reason or another.

Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand... by danielbarla on Friday April 01, 2016 @02:06AM (#11402990)
Having said that, I do wonder to what degree various database engines are aware of the underlying disk platforms.

I've definitely noticed that when optimizing a query and deciding between a high number of seeks vs. a table scan, older versions of MSSQL will tend to be pessimistic of drive latencies and just go with the full scan (potentially incorrectly / prematurely). In an uncached scenario on an SSD, this is probably sub-optimal. My guess would be that instead of looking at actual seek latency, the optimizer was using reasonable guesses for spinning disks. I'm guessing newer versions are more SSD aware though.

Re:Intel Xeon E5 v4 Review: Testing Broadwell-EP With Demand... by imaginenore on Thursday March 31, 2016 @08:17PM (#11401628)
But it looks like you're better off sharding your DB, instead of letting it use all the cores at once.