Live data from Hacker News

GPT-3.5 crashes when it thinks about useRalativeImagePath too much

iter.ca

21–30 of 164 posts

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#21
post #6

This is a glitch token [1]! As the article hypothesizes, they seem to occur when a word or token is very common in the original, unfiltered dataset that was used to make the tokenizer, but then removed from there before GPT-XX was trained. This results in the LLM knowing nothing about the semantics of a token, and the results can be anywhere from buggy to disturbing. A common example is usernames that participated on…

Aren’t there only 2^16 tokens? Seems easy to test for all of them, but I might just not understand the tokenizer.

Commenting to follow, curious about the answer.

From what I've found through Google (with no real understanding of llm) 2^16 is the max tokens per minute for fine tuning OpenAI's models via their platform. I don't believe this is the same as the training token count.

Then there's the context token limit, which is 16k for 3.5 turbo, but I don't think that's relevant here.

Though somebody please tell me why I'm wrong, I'm still trying to wrap my head around the training side.

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#23
post #21

Earlier quoted context omitted.

Aren’t there only 2^16 tokens? Seems easy to test for all of them, but I might just not understand the tokenizer.

Commenting to follow, curious about the answer. From what I've found through Google (with no real understanding of llm) 2^16 is the max tokens per minute for fine tuning OpenAI's models via their platform. I don't believe this is the same as the training token count. Then there's the context token limit, which is 16k for 3.5 turbo, but I don't think that's relevant here. Though somebody please tell me why I'm wrong,…

You are right to be curious. The encoding used by both GPT-3.5 and GPT-4 is called `cl100k_base`, which immediately and correctly suggests that there are about 100K tokens.

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#25
post #21

Earlier quoted context omitted.

Commenting to follow, curious about the answer. From what I've found through Google (with no real understanding of llm) 2^16 is the max tokens per minute for fine tuning OpenAI's models via their platform. I don't believe this is the same as the training token count. Then there's the context token limit, which is 16k for 3.5 turbo, but I don't think that's relevant here. Though somebody please tell me why I'm wrong,…

You are right to be curious. The encoding used by both GPT-3.5 and GPT-4 is called `cl100k_base`, which immediately and correctly suggests that there are about 100K tokens.

Amazing, thanks for the reply, I'm finding some good resources afyer a quick search of `cl100k_base`.

If you have any other resources (for anything AI related) please share!

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#26
post #16

Tried to use GPT-3.5 (all variants like turbo, 06-13, etc.) and never made it work properly. It is not a good API or useful. GPT-4 is crazy slow to use with API. I hope they can come up with something like gpt4-turbo and as fast as 3.5...

> GPT-4 is crazy slow to use with API

Only somebody clueless to just how powerful it is when used correctly would say anything like this. Not to mention GPT-4 Turbo is not "crazy slow" in any sense of the word

Post reply on HN