is a comprehensive book on getting a job at a top tech company, while focuses on dev interviews and does this for PMs.
CareerCup's interview videos give you a real-life look at technical interviews. In these unscripted videos, watch how other candidates handle tough questions and how the interviewer thinks about their performance.
Most engineers make critical mistakes on their resumes -- we can fix your resume with our custom resume review service. And, we use fellow engineers as our resume reviewers, so you can be sure that we "get" what you're saying.
Our Mock Interviews will be conducted "in character" just like a real interview, and can focus on whatever topics you want. All our interviewers have worked for Microsoft, Google or Amazon, you know you'll get a true-to-life experience.
Write-through Cache: Every write access to the Cache causes a write to main memory.
- Anonymous April 27, 2009Write-back Cache: Every write access to the Cache are not immediately written into main memory. Cache will write (dirty locations) into main memory some time later.
When a cache miss happens, a cache entry is evicted (in case of write-back cache and cache is full).
Replacement Policy (Evict Policy): When a memoy location is not present in the cache (called Cache miss), the cache creates a new entry. If all cache entries are used, the cache has to decide which existing entry should be removed to make room for cache miss. The rules used to evict cache entry is called Replacement Policy.
In a write-back cache, cache often requires 2 accesses to main memory. First access is to write the dirty locations of evicted entry into main memory. Second access is to read cache missed memory location from main memory to cache.