Open sujen1412 opened 6 months ago
We should somehow limit the number or size of inputs for this.. right? Like how do you estimate the “max running time”? From a UI perspective we may want to split this out of the big list of Resources and have a toggle for “Test run” or something like that, which would disable the Resource button
I could also imagine a queue for performance-testing to help estimate what size Resource you really need, or performance vs. price/etc. by kicking off the same job on multiple queues at once and giving you some metrics back. But that’s a separate thing
Currently, when testing a new/updated algorithm on the DPS, the user has to:
Most common errors in early testing include:
Proposal: Have a new maap-dps-sandbox queue with following features: