Live data from Hacker News

Price per 1M tokens is meaningless

janilowski.pl

81–90 of 113 posts

Re: Price per 1M tokens is meaningless

#81
post #70

Earlier quoted context omitted.

What incredible things can be done with it?

[flagged]

Would be easier to continue the conversation if you had answered their question though.

There's empirically someone up your comment saying that, better to address it with arguments rather than calling them brainrotted.

Re: Price per 1M tokens is meaningless

#83
Another thing I noticed is the llms perform efficiently/effectively only under the optimum circumstances. May be this just a Claude issue, but when the session goes on for very long the effectiveness drops drastically and I start getting bad answers. This is especially true for design and debugging. Wonder how that ladders up to the token usage

Re: Price per 1M tokens is meaningless

#84
post #72
post #69

On top of that isn't it strange that if the LLM makes a mistake you're still charged for those tokens? They're selling "intelligence", automation, etc but if the service doesn't work as expected the user has to pay for that.

If I use electricity to do something stupid, I still have to pay for the electricity. Intelligence is just another utility.

Spend 5 minutes on the marketing pages of any AI company and it's obvious they're not selling electricity, fuel, or even raw compute.

Re: Price per 1M tokens is meaningless

#85

I keep trying to convince directors and executives at my company to look past the cost per token amount but they refuse to do so. Those are the only things that actually give any sort of measurement of the monetary value of a token by these labs, and so its what many go by. For example there's some benchmarks that show that Opus for any task that requires a higher than `high` level of effort, may have actually been c…

What company is it, so I can compete with them? ;)

Re: Price per 1M tokens is meaningless

#86
post #24

I keep trying to convince directors and executives at my company to look past the cost per token amount but they refuse to do so. Those are the only things that actually give any sort of measurement of the monetary value of a token by these labs, and so its what many go by. For example there's some benchmarks that show that Opus for any task that requires a higher than `high` level of effort, may have actually been c…

> may have actually been cheaper to use Fable on low even though the cost per token is drastically higher Well that's the problem with these black boxes. You really have no idea beforehand how many tokens a given task is going to take. There's simply too many variables involved. It's therefore only natural for people to assume "the cheaper and older model is probably going to cost less overall to use than the newer,…

I'm definitely using more credit per task, using Fable, but I'm also giving it much more difficult tasks. You're right, it's very hard to tell. I think that using Opus would be more expensive because of the number of iterations I would need to go through.

Re: Price per 1M tokens is meaningless

#87
post #56

I feel we are caught in a "this is fine, pay more and we may turn down the fire" situation. The LLM itself produces one token. Some tool adds that token to the input and runs it again, flogging the horse. Downstream another tool, some kind of harness, tries to control this stream by injecting tokens into the context and then sending it to the inference tool, and then trying to pattern-match the output. Finally, there…

[flagged]

>Careful you don't "it's just a text predictor" yourself into unemployment .

says more than anything else could

Re: Price per 1M tokens is meaningless

#90

Earlier quoted context omitted.

So you are using a “cloud” provider and at 1c per million tokens … Love to hear more about how you structure the orchestrator etc

Yes, it's a "cloud provider" but it's a cloud provider running an open model you can download (and that other cloud providers do host). I just happen to not have a computer big enough to host it. As for the Orchestrator, it's pretty simple. In essence, it's like "Jira/Trello/Kanban on autopilot". Work items have states, a state machine defines how those work items transition between states, states are todo, in progre…

Ok, so I have to try that.

How are you specifiying the graphs? Is this on github (I am still trying to move from concept to how to actually do it (plus Inhave only just woken up and need coffee :-)

Post reply on HN