the built-in database only carries cards whose specs can be verified against a vendor sheet. but people have oc'd cards, laptop variants, and unreleased parts under nda.
idea: kernelmeter compare 4090 my-card --cards my-cards.json where the json holds the same physical fields as GpuSpec (sm_count, boost_mhz, mem_bus_bits, mem_gbps, tdp_w, cc). resolve() checks the user file first, then the built-in db.
keeps the built-in db strict while letting anyone model anything.
the built-in database only carries cards whose specs can be verified against a vendor sheet. but people have oc'd cards, laptop variants, and unreleased parts under nda.
idea: kernelmeter compare 4090 my-card --cards my-cards.json where the json holds the same physical fields as GpuSpec (sm_count, boost_mhz, mem_bus_bits, mem_gbps, tdp_w, cc). resolve() checks the user file first, then the built-in db.
keeps the built-in db strict while letting anyone model anything.