News for hackers. Stuff that matters.
Re:Moore’s Law Is About to Get Weird (2015) by pjc50 on Thursday August 04, 2016 @09:59AM (#12225510)
Asynchronous does not help you on latency at all - it's not the latency of the clock that matters. It's the data latency. This is already kind of crippling, as it takes hundreds of cycles to get anything from RAM if it's not in your cache.

Only way to improve that is to make programming languages push either data locality or dataflow like designs, which may mean giving up or reimagining OO.

Error rates (yield) are a serious problem, but if your design is uniform enough you can very well get away with just disabling bits. There's also a less obvious problem with on-chip variation (OCV) - some physical properties have a gradient across the chip. At runtime, there's a temperature gradient as well.

Re:Moore’s Law Is About to Get Weird (2015) by api on Thursday August 04, 2016 @10:03AM (#12225531)
Or... continuing with the BFC concept... make chips with monster caches or even with all SRAM running at core speed. That's not been done in a while.
Re:Moore’s Law Is About to Get Weird (2015) by pjc50 on Thursday August 04, 2016 @10:26AM (#12225724)
Caches effectively are SRAM. It's inherently much less dense than DRAM; I had a quick look on Intel and the largest I could see was 37Mb of cache.
Re:Moore’s Law Is About to Get Weird (2015) by n00b101 on Thursday August 04, 2016 @11:09AM (#12225996)
It's not SRAM, but Kights Landing has 16GB of "MCDRAM" which is high bandwidth 3D-stacked DRAM. 400+GB/s throughput but latency is similar to conventional DRAM.