You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
All that is still moving the data, with ever larger busses. I'm wondering if we can get away with not actually moving it, something like making DRAM refresh "smart" or "streaming".
The thing is DRAM doesn't spend a huge fraction of the time refreshing itself. DRAM is pipelined and you can stream data in/out of RAM pretty much as fast as the physical technology allows.
Exactly! The streaming of data in and out _is the bottleneck_. So add compute when you are already processing the data anyway.
I'm not convinced you could put enough useful compute in RAM chips to be useful. Sure, streaming workloads would benefit, but those often involve big fat SIMD instructions. And then you have to deal with cache coherency.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
