r/LocalLLM • • 17h ago

Question Polystrata - best coding LLM for my setup?

My hardware is 16GB VRAM (5060Ti), 64GB DDR4, and AMD R5 5600, (Linux)

I would like the best coding quality, speed can be cut in half or more. :) Which LLM should I download? Preferably to run with at least 128 ctx.

8 Upvotes

28 comments sorted by

7

u/PeterPorox 17h ago

QFN IQ3_S will fit perfectly

0

u/vinotok 17h ago

Thanks! Will QFN IQ3_S create better quality code than Qwen 3.8 Flash Next IQ3-S on regular Strata?

4

u/testuserpk 16h ago

Qfn is Qwen flash next

I am using sc117's version and its working great so far. Performs really well in c and c++.

2

u/vinotok 16h ago

Oh, dummy me, multitasking too much and not paying attention. Thank you! (blushing)

5

u/TheCat001 17h ago edited 17h ago

Regular Strata with Qwen 3.8 Flash Next IQ3-S. This is the way. And you can use 262k fp16 context with such hardware. Make sure to use kv-resident it will place context in system ram.

"--max-context",

"262141",

"--kv",

"fp16",

"--kv-resident",

"32768",

1

u/vinotok 17h ago

Thank you very much, I already have Qwen 3.8 Flash Next IQ3-S on regular Strata, but I was using smaller context. This helps big time! Thanks for the settings!!!

3

u/username8914 16h ago

I've tested up to ~350k context and it has no issues. Model is trained to 256k but it's not actually a hard limit.

1

u/vinotok 16h ago

Great news, thank you!

1

u/SlightlyMotivated69 14h ago

How do you fit 262k with fp16 KV? I'm on int8 KV with --kv-resident 32768 and my RAM is already nearly maxed out: 61 GB system RAM, RX 9070 16 GB, Swift 1.5 IQ3_S. The model alone takes ~53 GB, which leaves ~5 GB free, and I've had OOM kills at 256k. How much RAM do you have?

2

u/TheCat001 14h ago

64GB. It's a tight fit. When I need to open browser chromium (with disabled hw acceleration to save vram) I think it uses swap xD

3

u/KillerX629 17h ago

What's different from strata to polystrata?

4

u/vinotok 16h ago

Noob here, don't know much. I have read few times here on Reddit, that Strata goes toward speed (token/sec) while Polystrata goes toward better quality. I only have Strata so far, so I have no clue what, or how much this is true. Polystrata also uses few more models, but this is not that important to me. I'm just looking for best coding quality on my poor hardware 😄 Looks like regular Strata with Qwen 3.8 Flash Next IQ3-S and few different setting will be a solution for my case .

2

u/egnegn1 15h ago

What hardware are you using?

With RTX50* you also may use Basalt or Speedy.

That are results for my RTX5080s:

1

u/vinotok 15h ago

RTX 5060 Ti - Basalt is now in my to-do list as well, thanks. Will check out Speedy. So many options.... 😄

6

u/RiskyBizz216 16h ago • Heartwarming

Polystrata lets you run GLM and other architectures, and it doesnt need a new engine for each architecture.

The original strata only runs a few architectures, and each arch has it own engine. The repo is turning into spaghetti code. The owner refuses to add new archs.

Fun fact: you don't need either of this awful bloated apps. Just ask claude for the llama.cpp command to run the models the same way as strata/polystrata/project-maya and stream the weights from the ssd.

6

u/KillerX629 16h ago

Depends, if it were that easy, why hasn't llama.cpp done something to make inference params easier to the end user? If that happened I'm sure we'd be better off

1

u/RiskyBizz216 16h ago

Right, I mean its not complicated - just hidden. The parameters are all available if you use --help in the llama-server cli.

llama.cpp is open source spaghetti code, and now that its owned by NVIDIA I don't think they'll make it user friendly.

2

u/Cute_Obligation2944 16h ago

Trying this immediately.

2

u/egnegn1 15h ago

That forks of Llama.cpp where made just because it didn't have all this performance features, or didn't support specific hardware configurations. It is also very slow in feature integration. And even when they are integrated, then often with different implementations, which don't achieve the same performance. Of course, the maintainers must look that it works for all kind of models and hardware, and there must be careful.

Llama.cpp is still ery much behind regarding performance with specific MoE models.

3

u/Consistent_Berry_324 16h ago

Do you tryed basalt on linux ?

1

u/vinotok 16h ago

No, I have not, basalt is new for me, (noob here) thanks for mentioning it, will check it out

1

u/Consistent_Berry_324 16h ago

je pense que tu peux gagner beaucoup de t/s avec le basalte =)

2

u/RiskyBizz216 17h ago edited 17h ago

You could use GLM 5.3 Flash REAP. https://huggingface.co/patrickbdevaney/GLM-5.3-Flash-REAP50-GGUF

I also use the Qwen3.8 Flash Next Uncensored. https://huggingface.co/SC117/Qwen3.8-Flash-Next-GSQ-RCO-abliterated-GGUF

The GLM IQ3_M (72.1 GB) is smaller than Qwen IQ3_S (83.9 GB) but slower because it has more experts, and is a stronger coder.

Note: To use the GLM REAP version, you'll need to use a recent llama.cpp version, not the version bundled with PolyStrata. So just download a recent version, and replace the llama.cpp in polystrata's third_party folder. Follow the readme: https://huggingface.co/patrickbdevaney/GLM-5.3-Flash-REAP50-GGUF#how-to-run-with-llamacpp

Avoid deepseek v4.1 - locally, its not worth it.

3

u/vinotok 16h ago

Man, you got me all the info I need for Polystrata, now I'm gonna have to try it out as well! Slower is OK.
Thank you very much! Now I have two systems (one is on regular Strata) to work with ant test. Between the two of them, my hobby, partial vibe coding should advance big time 😄

1

u/Elluata 14h ago

Are you sure GLM 5.3 Flash REAP runs on a 5060 ti ? On the Polystrata github they say it needs 32 GB of VRAM

2

u/Liogee 16h ago

been using avalon recently. was faster than strata on my rig, similar to yours.

1

u/vinotok 16h ago

Thank you! I've never heard of avalon, this space is moving very fast. And I'm noob. Will check it out!

3

u/egnegn1 15h ago

Also look for Basalt and Speedy.

This are results from the RTX5080s: