CapordiaDefine the expected outcome
Start with a concrete sentence: process a set of documents, maintain an environment for a week, or produce a series of results before a given date. Add the users involved and the person who will verify that the work is complete. An operational description makes it easier to choose a duration as well as a card.
State what is known and what still needs to be measured. The software and its version, input sizes, observed memory peak, and task frequency are useful information. An unknown value can remain an open point; the goal is to organize its verification.
Map constraints to the catalog
Review the memory per GPU, the number of cards needed, and software compatibility. Distinguish a workload that fits on one card from independent tasks you want to run in parallel. Then choose a 3, 7, or 30-day period, taking into account preparation and the final export.
Write the acceptance criteria
Choose a few checks the team can actually perform: load a test set, run the planned process, retrieve the outputs, and resume after a deliberate stop. Name the person responsible for each check. This gives you a usable document to compare models, prepare deployment, and explain the choice made.