If some other entity (Government agency? Another company?) Comes around to pull this string, its going to set a bad precedent.
7,874 karma · joined February 13, 2023
If some other entity (Government agency? Another company?) Comes around to pull this string, its going to set a bad precedent.
- B: Yes, uploading via a web page would be nice too. I have seen other apps do this.
I have used such apps before, but it seems they have gone unmaintained and don't work anymore.
Meanwhile, Yi-34B-200K has been updated:
> In the "Needle-in-a-Haystack" test, the Yi-34B-200K's performance is improved by 10.5%, rising from 89.3% to an impressive 99.8%. We continue to pretrain the model on 5B tokens long-context data mixture and demonstrate a near-all-green performance.
I am particularly excited for this, as Yi 34B 200K finetunes are already my favorite non coding models, even including 70Bs. And its just about perfect for a 24GB consumer card (which I can cram about 75K onto without too much compromise).
I wouldn't be surprised if they could double performance.
I know Apple is pushing MLX, and MLC-LLM is fast too, but in practice most Mac users (I think) are using llama.cpp based stacks.
Enthusiasts in a subject are often wrong, but usually the goal is at least to convey something useful about the topic to the reader.
The spammer/content farmer doesn't care about that. Users trying to farm attention on social media don't care about that. A manipulator on a certain topic doesn't care about that. They just want SEO and eyeballs. But usually the intersection between high quality topical writers and people with these motivations is very low.
...That is not the case any more.
Generic social media is going to be a hellscape, yes, but I think weird niches could still thrive if Discord wasn't walling them off.
Running one as a background desktop assistant is whole different animal than calling a Microsoft API.
That calculus totally changes with 48GB. I would put up with A LOT of trouble for that.
48GB consumer cards (or 96GB pro cards) would sell like hotcakes if AMD/Intel dare to break the artificial VRAM segmentation status quo.
Thats how you get electromigration.
I would suggest AMD's X3D-only CPUs instead (which stick to very reasonable clocks/voltages), but I guess there's a risk of the stacked die failing as well.
Now, what's a little odd to me is that there was so much interest positive interest from HNers? People submit really good new models/finetunes all the time, but there's usually no interest in them, at least not unless I bring them up in tangentially related comment sections.
But GGUF Mixtral should fit in 32GB... just not with the full 32K context. Long context is very memory intense in llama.cpp, at least until they fully implement flash attention and a quantized cache.
Miqu 70B is slow (less than 10 tok/sec, I think) because I have to split it with llama.cpp. I only use it for short context questions where I need a bit more intelligence.
And for reference, this is a SFF desktop! It's no Macbook, but still small enough (10L and flat) for me to fly with in carry on.
They don't have the augmentations of being a service, but generally they are smarter, have a bigger context and (perhaps most importantly) are truly unbound.
I am on a single 3090 desktop, for reference. Admittedly, this is much more expensive now than it was a few months ago, with the insane prices used 3090s are going for now.
- Local models are pretty easy to de-censor, if thats what you mean.
- ...Yeah, it should not be labeled as a 7B. Its sort of 7B class.
- The repo mentions they use the llama-cpp-python server
- 1M context brute forced across TPUs is insanely expensive, I can see why Google reigned it in.
But overall your message is not wrong. Google is hyping Gemma a ton when its... Well, not very remarkable. And they could have certainly made something niche and interesting, like a long context 8.5B model, a specialized model, a vastly more multilingual model, something to differentiate it from Mistral 7B 0.2
I can't share the eval, but it's pretty simple: it asks a question about some data, and is restricted to only answer yes/no (based on the output logits and suggested in the prompt). It's called with 0 temperature and only 1 output token, so sampling shouldn't be an issue.
As I said, the entire world needs to shift how they percieve digital media. People are used to seeing a photo/video and thinking of it as representing something real... that's not the case. Now it's a fantasy, with the degree depending on the source.
Think ya'll will ever offer single MI300X instances?
Also, there's a lot of magic going on behind the scenes with configs stored in gguf/huggingface format models, and the libraries that use them. There are different tokenizers, but they mostly follow the same standards.
One thing I do suspect people are running into is sampling issues. Gemma probably doesn't like llama defaults with its 256K vocab.
Many Chinese llms have a similar "default sampling" issue.
But our testing was done with zero temperature and constrained single token responses, so that shouldnt be an issue.
And yes, this was an amazing landing and proof of the tech.