feat(inference): redesign historical gpu comparison view

[rafaykhan-source]

Redesign Historical GPU Comparison View

Many users select a GPU to compare but then struggle with the date range and intermediate-date selection, and the date-selection shortcut buttons are largely ignored. Come up with a design for a better implementation.

The priority audience is technical users who use the site frequently and want to move fast through repeated comparisons, without alienating first-time visitors who don't yet know the data model.

Requirements + Reasoning

1. A fast, low-friction flow for repeat users. Picking a GPU or GPUs and exploring their history over time should take few clicks, with sensible defaults and keyboard-friendly affordances where it helps.

• In the redesign, we switch from the drop down multi-select for GPUs to multiple drop-downs with mutual exclusivity. This would allow technical users to quickly pick two GPUs, and spells out to first-time users that it is explicitly for comparison.

Before:

After:

2. Approachable enough that a first-time visitor can pick a GPU and land on a meaningful curve-over-time view without having to fully understand the date model up front.
3. Date range and intermediate-date selection should feel obvious; the existing shortcut buttons should either be redesigned to actually get used or replaced with something better.

• In the redesign, instead of blurring out the charts and fields upon only clicking one GPU, it now will auto-select a date range (all time), so that first time users need not understand the data model, and technical users have the convenience of using the date comparison shortcut buttons without having open the calendar modal.

Before:

After:

5. Whatever shape the new selection takes, it must roundtrip through the URL so shared links reproduce the exact view.

• The redesign, only reorganizes the existing selection queries for URL roundtripping.

7. Consider splitting into a latest data view tab and historical data view tab?

• In favor of not disrupting the flow of technical users to who use the site frequently, I choose to maintain the locality of the options on the page, but separate the concerns clearly (in two different cards) to express the same clarity that would be achieved by two views. I'm definitely open to splitting them, but with five existing tabs on the dashboard things could get unwieldy.

8. Analytics events on the new selection affordances so we can measure whether the redesign actually moved usage.

• The new analytics events were added and instrumented with track()

User Flow

Before:
https://github.com/user-attachments/assets/2afc99a2-6287-417e-b753-324afc588e04

After:
https://github.com/user-attachments/assets/9613d063-11ef-4d26-b39d-8042a36cfddb

Closes #273

[vercel]

@rafaykhan-source is attempting to deploy a commit to the SemiAnalysisAI Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
inferencemax-app	Ready	Preview, Comment	May 9, 2026 11:01pm