Greetings from the Gemma team! We just got Gemma 3 out of the oven and are super excited to show it to you! Please drop any questions here and we'll answer ASAP. (Opinions our own and not of Google DeepMind.) PS we are hiring: https://boards.greenhouse.io/deepmind/jobs/6590957
Gemma 3 Technical Report [pdf]
211–220 of 260 posts
Re: Gemma 3 Technical Report [pdf]
#212https://garden.tcsenpai.com/bookmarks/ai/ai-convos-notes/gem...
Re: Gemma 3 Technical Report [pdf]
#213Earlier quoted context omitted.
I don't disagree but even Linux has "Terms and conditions" of usage under it's license you really need to dig into what those are. There's no doubt Gemma's license is less permissive than other models and that it has less community finetuners for that reason.
can you link to Linux terms and conditions? search returned nothing.
Re: Gemma 3 Technical Report [pdf]
#214Per quick testing the 27b model seems very strong at least in natural language. It produces even good Finnish, in which smaller models tend to really struggle. Very promising. Edit: Per even quicker testing the Finnish language performance degrades rapidly with the smaller models, as is usually the case. Would be great to have language specific distillations from larger models.
How does it compare to Deepl for Finnish ?
Re: Gemma 3 Technical Report [pdf]
#215Earlier quoted context omitted.
I don't disagree but even Linux has "Terms and conditions" of usage under it's license you really need to dig into what those are. There's no doubt Gemma's license is less permissive than other models and that it has less community finetuners for that reason.
can you link to Linux terms and conditions? search returned nothing.
Re: Gemma 3 Technical Report [pdf]
#216Re: Gemma 3 Technical Report [pdf]
#217For someone jumping back on the local LLM train after having been out for 2 years, what is the current best local web-server solution to host this for myself on a GPU (RTX3080) Linux server? Preferably with support for the multimodal image input and LaTeX rendering on the output.. I don't really care about insanely "full kitchen sink" things that feature 100 plugins to all existing cloud AI services etc. Just running…
Ollama + open web-ui in a container https://ollama.com/ https://github.com/open-webui/open-webui
https://github.com/likelovewant/ollama-for-amd/wiki#demo-rel...
I specifically recommend the method where you grab the patched rocblas.dll for your card model, and replace the one that Ollama is using, as someone who is technical but isn’t proficient with building from source (yet!)
Re: Gemma 3 Technical Report [pdf]
#218What do companies like Meta and Google gain from releasing open models? Is it just reputational? Attractive to top AI talent?
I believe (and some other people on the internet having more knowledge in LLM believe too) that open source local models are the future. Probably big models with API and chat like OpenAI is doing will have its niche toot but it is very costly and it is not AGI and it will not be in the near future. On the other hand with rise of NPU chips and small models you can have your own assistant on your phone using your own d…
Re: Gemma 3 Technical Report [pdf]
#219For someone jumping back on the local LLM train after having been out for 2 years, what is the current best local web-server solution to host this for myself on a GPU (RTX3080) Linux server? Preferably with support for the multimodal image input and LaTeX rendering on the output.. I don't really care about insanely "full kitchen sink" things that feature 100 plugins to all existing cloud AI services etc. Just running…
Ollama + open web-ui in a container https://ollama.com/ https://github.com/open-webui/open-webui
Re: Gemma 3 Technical Report [pdf]
#220It's surprisingly fast and pretty good. Was really impressed that I can feed it images through open-webui
However, it keeps failing, both on the terminal and through open-webui. The error is:
"Error: an error was encountered while running the model: unexpected EOF"
It seems like it's an ollama issue, although according to tickets on GitHub it's supposed to be related to CUDA, but I'm running it on an M3 Mac
Up until now I never had this issue with ollama, I wonder if it's related to having updated to 0.6.0