Very broken: "live minimums" do not allow me to remove 512 token limit and put a bigger number easily.

No unified or shared memory scenarios (like Apple's M platform or AMD's integrated GPU platform).

Was going to mention this. I'm on an M1 Max and wanted to see what the site suggested.

actually that input is broken. and sorry for that. and I am adding shared memory features in next iterations.

that broken input is fixed

very nice idea. Would be nice if you could also keep desired context as a free parameter and let the models tell you what maximum context you could have.

actually that's free by design, it is just broken. fixing it in next sprint. And really thanks for your feedback!!!

now that is fixed, please try it

Awesome, how do I contribute to this? A gihub link or smthg?

actually, currently it is not open source, but I am thinking about making it open source so that other developers can also contribute in it(espeically data layer). what do you think?

Yes, many people like myself are willing to contribute. It'll take the load off you and give you time to work on other features or projects.

handy, but the gap most of these filters have is that "fits in VRAM" doesn't mean usable. context length blows up the KV cache fast, a 7B that fits at 2k tokens will OOM at 32k. factoring context len + quant into the estimate is where it'd actually save people from getting burned.

i think you did not check app properly, it is actually taking required context window from the user and then caluclate kv cache size and then count it along with size of model itself. it also reserves some more memory to avoid oom....