Skip to content

Computer Science Final Year Topic: Design and Evaluation of Cache Eviction Policy Benchmark

This Computer Science final year project investigates retaining useful objects when application cache capacity is limited, with an explicit prototype scope and a reproducible evaluation plan.

Why choose this project topic?

The practical value of this topic lies in retaining useful objects when application cache capacity is limited. It gives a student a demonstrable computing problem, with hit ratio, eviction cost and memory overhead providing concrete evidence for a critical project discussion.

Which eviction policy performs best under changing locality in synthetic access traces?

Agree the available tools, workload size and evaluation criteria with your supervisor; adapt retaining useful objects when application cache capacity is limited to a clearly bounded institutional or laboratory setting.

Proposed project objectives

  1. 01Specify the requirements and assumptions for retaining useful objects when application cache capacity is limited.
  2. 02Implement least-recently-used, frequency-based and random eviction, replay identical traces and vary cache size with warm-up periods reported.
  3. 03Evaluate hit ratio, eviction cost and memory overhead against a documented baseline and discuss failure cases.

A suggested research approach

Implement least-recently-used, frequency-based and random eviction, replay identical traces and vary cache size with warm-up periods reported. Record the chosen implementation, dataset construction and repeatable test conditions before comparing hit ratio, eviction cost and memory overhead. Keep development and evaluation cases separate where possible, and retain failed cases in the analysis rather than reporting only successful demonstrations.

What you will need

  • Synthetic object access traces
  • Cache policy implementations
  • Repeatable benchmark runner

Keep your project scope clear

Trace-based results cannot predict every production workload or storage hierarchy. A project write-up does not supply a working application.

Computer Science project chapter outline

Use this outline as a starting point. You can edit the chapter titles to match your department’s format during setup.

  1. Chapter 1Introduction
  2. Chapter 2Literature Review
  3. Chapter 3System Analysis and Design
  4. Chapter 4System Implementation and Testing
  5. Chapter 5Summary, Conclusion and Recommendations

Turn this topic into your own final year project.

Your title, department, research question and outline are ready. Add your institution, personalise the details and continue to your project workspace.

Generate the Complete Project Generation uses your word balance. Review the draft and supply your own verified research findings.