News for hackers. Stuff that matters.
Re:Qwen2.5-1M: Deploy your own Qwen with context length up t... by jkbbwr on Sunday January 26, 2025 @03:28PM (#42833754)
Everyone keeps making the context windows bigger, which is nice.

But what about output? I want to generate a few thousand lines of code, anyone got any tips?

Re:Qwen2.5-1M: Deploy your own Qwen with context length up t... by mmaunder on Sunday January 26, 2025 @03:32PM (#42833779)
Repeatedly ask it for more providing the previous output as context. (Back to context length as a limitation)
Re:Qwen2.5-1M: Deploy your own Qwen with context length up t... by anotheryou on Sunday January 26, 2025 @03:32PM (#42833776)
Isn't that the same? limit-wise.

Now you just need to convince it to output that much :)

Re:Qwen2.5-1M: Deploy your own Qwen with context length up t... by bugglebeetle on Sunday January 26, 2025 @03:37PM (#42833822)
So context size actually helps with this, relative to how LLMs are actually deployed as applications. For example, if you look at how the “continue” option in the DeepSeek web app works for code gen, what they’re likely doing is reinserting the prior messages (in some form) to a new one to prompt further completion. The more context size a model has and can manage successfully, the better it will likely be able at generating longer code blocks.
Re:Qwen2.5-1M: Deploy your own Qwen with context length up t... by nejsjsjsbsb on Monday January 27, 2025 @02:44AM (#42838434)
Isn't input/output lengths an arbitrary distinction. Under the hood, output becomes the input for the next token at each step. OpenAI may charge you more $$ by forcing you to add output to the input and call the API again. But running local you don't have that issue.
Re:Qwen2.5-1M: Deploy your own Qwen with context length up t... by AyyEye on Sunday January 26, 2025 @03:34PM (#42833795)
These things already produce embarrassing output. If you make it longer it's just going to get worse.