It makes sense to take cost per task more important than cost per token, but for long running tasks, are more appropriate indicator could be "cost per accepted outcome". Because for a task, it is hard to say:
What is the boundary of the task?
Do we count failure and retry as the same task?
What if the result "looks" good but rejected by the user?
How do we measure the extra human effort for verifying and resuming when using the cheap model?
In my opinion, "cost" means more than the direct token usage of a finished task.
6 comments
[ 0.52 ms ] story [ 17.1 ms ] threadWhat is the boundary of the task?
Do we count failure and retry as the same task?
What if the result "looks" good but rejected by the user?
How do we measure the extra human effort for verifying and resuming when using the cheap model?
In my opinion, "cost" means more than the direct token usage of a finished task.
I wonder how you come you opted for GLM; how did the selection process look like?