←back to thread

237 points JnBrymn | 2 comments | | HN request time: 0s | source
Show context
sabareesh ◴[] No.45675879[source]
It might be that our current tokenization is inefficient compared to how well image pipeline does. Language already does lot of compression but there might be even better way to represent it in latent space
replies(3): >>45675953 #>>45676049 #>>45677115 #
ACCount37 ◴[] No.45675953[source]
People in the industry know that tokenizers suck and there's room to do better. But actually doing it better? At scale? Now that's hard.
replies(1): >>45676189 #
typpilol ◴[] No.45676189[source]
It will require like 20x the compute
replies(3): >>45676906 #>>45676935 #>>45676964 #
1. kenjackson ◴[] No.45676964[source]
Why so much compute? Can you tie it to the problem?
replies(1): >>45679126 #
2. typpilol ◴[] No.45679126[source]
Tokenizers are the reason LLMs are even possible to run at a decent speed on our best hardware.

Removing the tokenizer would 1/4 the context and 4x the compute and memory, assuming an avg token length of 4.

Also, you would probably need to 4x the parameters to have to learn understanding between individual characters as well as words and sentences etc.

There's been a few studies on small models, even then those only show a tiny percentage gain over tokenized models.

So essentially you would need 4x compute, 1/4 the context, and 4x the parameters to squeeze 2-4% more performance out of it.

And that fails when you use more then 1/4 context. So realistically you need to support the same context, so you r compute goes up another 4x to 16x.

That's why