Skip to content

Computer Engineering Final Year Topic: Design and Evaluation of Hardware Performance Counter Study

This Computer Engineering final year project investigates relating measured cache and branch events to bounded benchmark behaviour, linking hardware behaviour and software assumptions through an explicitly bounded prototype or simulation.

Why choose this project topic?

The topic makes relating measured cache and branch events to bounded benchmark behaviour a testable computer-engineering problem with visible interfaces and failure cases. Measuring counter repeatability, runtime variation and event correlation helps a student compare design alternatives and explain how resource constraints affect the proposed implementation.

How do the selected hardware or embedded-software choices affect counter repeatability, runtime variation and event correlation when relating measured cache and branch events to bounded benchmark behaviour?

Choose an available development board or simulator, agree the supported interface and workload, and narrow relating measured cache and branch events to bounded benchmark behaviour with your supervisor.

Proposed project objectives

  1. 01Specify the interfaces, operating assumptions and expected behaviour for relating measured cache and branch events to bounded benchmark behaviour.
  2. 02Run permitted microbenchmarks on an authorised computer, repeat controlled workloads and compare counter patterns with source-level expectations.
  3. 03Measure counter repeatability, runtime variation and event correlation and document failures, resource limits and reproducibility.

A suggested research approach

Run permitted microbenchmarks on an authorised computer, repeat controlled workloads and compare counter patterns with source-level expectations. Keep all tests on owned, simulated or approved low-voltage equipment. Record hardware and tool versions, compare output with an independent reference, and evaluate counter repeatability, runtime variation and event correlation using normal, boundary and interrupted-operation cases.

What you will need

  • Authorised test computer
  • Permitted microbenchmarks
  • Performance profiling tools

Keep your project scope clear

Counter correlations do not prove a single causal bottleneck and depend on the processor model. Project writing does not supply working firmware or manufactured hardware.

Computer Engineering 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 3Materials and Methods
  4. Chapter 4Results and Discussion
  5. Chapter 5Conclusion 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.