A few people here tried the Goliath-120B model I released a while back, and looks like TheBloke has released the quantized versions now. So far, the reception has been largely positive.

https://huggingface.co/TheBloke/goliath-120b-GPTQ

https://huggingface.co/TheBloke/goliath-120b-GGUF

https://huggingface.co/TheBloke/goliath-120b-AWQ

The fact that the model turned out good is completely unexpected. Every LM researcher I’ve spoken to about this in the past few days has been completely baffled. The plan moving forward, in my opinion, is to finetune this model (preferably a full finetune) so that the stitched layers get to know each other better. Hopefully I can find the compute to do that soon :D

On a related note, I’ve been working on LLM-Shearing lately, which would essentially enable us to shear down a transformer down to much smaller sizes, while preserving accuracy. The reason goliath-120b came to be was an experiment in moving at the opposite direction of shearing. I’m now wondering if we can shear a finetuned Goliath-120B to around ~70B again and end up with a much better 70B model than the existing ones. This would of course be prohibitively expensive, as we’d need to do continued pre-train after the shearing/pruning process. A more likely approach, I believe, is shearing Mistral-7B to ~1.3B and perform continued pretrain on about 100B tokens.

If anyone has suggestions, please let me know. Cheers!

  • ReturningTarzan@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    If anyone has suggestions, please let me know. Cheers!

    The suggestion I’d give, apart from finetuning, would just be to do some actual tests. Construct some scenarios that test the model’s ability to “show not tell” and so on, and contrast with smaller models and/or with a “null hypothesis” Frankenstein model where the added layers are just random matrices, etc.

    Ideally, if there’s nothing you can do to objectively measure the model’s performance, try to set up a blind test of some sort to see if users actually prefer the Frankenstein model over the two models it was spliced together from.

    Not to disparage the project or anything, but confirmation bias is a real thing, and it’s especially rampant in the LLM space.