baltort wrote:There seems to be lots of confusion about the units used on ORC. I might be being pedantic about this, but I read OB/hour as OctaneBench PER hour. I think it should be Octane Bench Hours (perhaps written as OB.hours) since this is the value that represents actual computing effort and that is what cloud users are paying for.
OctaneBench is a measure of rendering speed (Sampled Rays/s) and multiplying this by time (e.g. 60 minutes) is the unit of work you are paying for on ORC.
if the job is scheduled for same day turnaround (the default), then a 1 hr job @ 1000 OB , pretty much is the same result/cost to the customer as a 4 hour job @ 250 OB - but internally we may use this shift to help load balance smaller jobs with much much bigger ones that come in that day (which may need hundreds or thousands of GPUs at once to get a job done in a day or less). If capacity is tight in any given day, priority is given to larger jobs in the order they come in, and results may be pushed out beyond a day (rare but possible). If we have high availability your render may get started and finished very quickly, much sooner than the default 1 day turnaround.