Atomic operations are expensive, even if there is no contention with other threads. Please don't use them in serial code (this includes std::shared_ptr). Tested on Intel Core i7-5820Kpic.twitter.com/SShUepjp2Y
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
Is there a lot of room for them to get faster? Isn't the lower bound around the cost of a cache miss? We try to avoid cache misses, so why not try to avoid unnecessary interlocked ops too?
A CPU’s speculative execution *could* plow through an interlocked operation or atomic block at full speed, and only backtrack if there’s contention. Speculative concurrency control is the most vital current topic in CPU design.
hmmm same logic can be applied to UWP and Windows Store .. " the more you use it (as developers) the more MS will fine tune it to meet your needs/wants" ... seems logical!
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.