The warm up is just the period of loading a set of data so that the cache gets populated with valid data. If you’re doing performance testing against a system that usually has a high frequency of cache hits, without the warm up you’ll get false numbers because what would normally be a cache hit … Read more
“traversing” just means looping over the data. And yes, you’re right about cache ways and collisions. 64B (cache line size) blocks of memory that are offset from each other by a large power of 2 map to the same set, and thus compete with each other for ways in that set, instead of being cached … Read more
The main reason is: performance. Another reason is power consumption. Separate dCache and iCache makes it possible to fetch instructions and data in parallel. Instructions and data have different access patterns. Writes to iCache are rare. CPU designers are optimizing the iCache and the CPU architecture based on the assumption that code changes are rare. … Read more
I might be writing this a bit late but just in case anybody looking for a solution soon. By the moment the official video_player plugin doesn’t support video caching over network yet. But fortunately, there been some attempts by contributors to add caching feature to the video_player plugin You can track updates and find another … Read more
We have done recently a fair amount of comparing of Velocity and Memcached. In the nutshell, we found Velocity to be 3x – 5x slower than Memcached, and (even more crucially) it does not have currently support for a multi-get operation. So at the moment, I would recommend going with Memcached. Also, another lesson we … Read more
The warning issued by mysqltuner.py is actually relevant even if your cache has no risk of being swapped. It is well-explained in the following: http://blogs.oracle.com/dlutz/entry/mysql_query_cache_sizing Basically MySQL spends more time grooming the cache the bigger the cache is and since the cache is very volatile under even moderate write loads (queries gets cleared often), putting … Read more
Out of the box? You can’t. But you can extend the BladeCompiler class, overriding the method resposible for checking if the view has been expired: class MyBladeCompiler extends BladeCompiler { public function isExpired($path) { if ( ! \Config::get(‘view.cache’)) { return true; } return parent::isExpired($path); } } You’ll need to replace the BladeCompiler instance in IoC … Read more
The answer to your question is – it depends. That’s strictly a CPU design decision, which balances over the tradeoff between performance and complexity. Take for example recent Intel Core processors – they’re physically tagged and virtually indexed (at least according to http://www.realworldtech.com/sandy-bridge/7/). This means that the caches can only complete lookups in pure physical … Read more