SHARK
llama
SHARK | llama | |
---|---|---|
84 | 184 | |
1,393 | 53,502 | |
2.2% | 3.2% | |
9.4 | 8.1 | |
7 days ago | 8 days ago | |
Python | Python | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SHARK
- Llama 2 on ONNX runs locally
-
[D] Confusion over AMD GPU Ai benchmarking
https://github.com/AUTOMATIC1111/stable-diffusion-webui, https://github.com/nod-ai/SHARK, those are the repos for the open source tools mentioned. u/CeFurkan has really nice tutorial videos on YouTube for stable diffusion. Automatic1111 is the most popular open source stable diffusion ui and has the biggest open source plug-in ecosystem currently. Nvidia’s compute driver is separate from normal driver and called cuda. Amd’s compute driver is called rocm. Most windows programs like games use apis like directx, Vulkan,metal, web gpu and not cuda. Most ml code was originally intended to run in on scientific computing systems that were Linux. Today the traditional windows gpu apis are tying to get better at gpu ml supports. Amd has no official windows ml code support and is Hoping that other developers figure it out for them but amd made their ml driver open source but no support for consumer graphics cards. Nvidia is proprietary ml driver but guaranteed support across all cards including consumer
-
Amd Gpu not utilised
I got it working using SHARK with an AMD RX 480 on Windows 10.
-
New to SD - Slow working
Here the link for shark, faster (uses vulkan) than automatic1111 with directml but has less functions https://github.com/nod-ai/SHARK
-
7900 XTX Stable Diffusion Shark Nod Ai performance on Windows 10. Seem to have gotten a bump with the latest prerelease drivers 23.10.01.41
I would recommend trying out Nod AI's Shark (That is the link for the most recent 786.exe release), and see how it works for you. From others I've read, it does 512x512 pics at around 3 it/s, which I know isn't mind blowing, but it's good enough to do a pic in about 30 seconds.
-
New here
Problem solve, i had it to work i simply put this nod's ai shark exe in my stabble diffusion folder and launch it instead of Webui-user -> Release nod.ai SHARK 20230623.786 · nod-ai/SHARK (github.com)
-
I built the easiest-to-use desktop application for running Stable Diffusion on your PC - and it's free for all of you
How does it compare with Shark SD (I am not affiliated with it in any way)? (https://github.com/nod-ai/SHARK)
-
after changing GPU from RX 470 4gb to RTX 3060 12GB, I decided to make a few cozy houses, and these are a few of them
you should if you want to run SD on your card https://github.com/nod-ai/SHARK
-
20 minute load time per image on high end pc?
Forgive me for not reading you whole comment. I suspect you're version of the SD eb UI doesn't recognize the AMD GPU., so you're using the CPU. AMD GPUs only work with a few web UIs. Try Nod.ai's Shark variant
- AMD support for Microsoft® DirectML optimization of Stable Diffusion
llama
-
Mark Zuckerberg: Llama 3, $10B Models, Caesar Augustus, Bioweapons [video]
derivative works thereof).”
https://github.com/meta-llama/llama/blob/b8348da38fde8644ef0...
Also even if you did use Llama for something, they could unilaterally pull the rug on you when you got 700 million years, AND anyone who thinks Meta broke their copyright loses their license. (Checking if you are still getting screwed is against the rules)
Therefore, Zuckerberg is accountable for explicitly anticompetitive conduct, I assumed an MMA fighter would appreciate the value of competition, go figure.
-
Hello OLMo: A Open LLM
One thing I wanted to add and call attention to is the importance of licensing in open models. This is often overlooked when we blindly accept the vague branding of models as “open”, but I am noticing that many open weight models are actually using encumbered proprietary licenses rather than standard open source licenses that are OSI approved (https://opensource.org/licenses). As an example, Databricks’s DBRX model has a proprietary license that forces adherence to their highly restrictive Acceptable Use Policy by referencing a live website hosting their AUP (https://github.com/databricks/dbrx/blob/main/LICENSE), which means as they change their AUP, you may be further restricted in the future. Meta’s Llama is similar (https://github.com/meta-llama/llama/blob/main/LICENSE ). I’m not sure who can depend on these models given this flaw.
-
Reaching LLaMA2 Performance with 0.1M Dollars
It looks like Llama 2 7B took 184,320 A100-80GB GPU-hours to train[1]. This one says it used a 96×H100 GPU cluster for 2 weeks, for 32,256 hours. That's 17.5% of the number of hours, but H100s are faster than A100s [2] and FP16/bfloat16 performance is ~3x better.
If they had tried to replicate Llama 2 identically with their hardware setup, it'd cost a little bit less than twice their MoE model.
[1] https://github.com/meta-llama/llama/blob/main/MODEL_CARD.md#...
-
DBRX: A New Open LLM
Ironically, the LLaMA license text [1] this is lifted verbatim from is itself copyrighted [2] and doesn't grant you the permission to copy it or make changes like s/meta/dbrx/g lol.
[1] https://github.com/meta-llama/llama/blob/main/LICENSE#L65
-
How Chain-of-Thought Reasoning Helps Neural Networks Compute
This is kind of an epistemological debate at this level, and I make an effort to link to some source code [1] any time it seems contentious.
LLMs (of the decoder-only, generative-pretrained family everyone means) are next token predictors in a literal implementation sense (there are some caveats around batching and what not, but none that really matter to the philosophy of the thing).
But, they have some emergent behaviors that are a trickier beast. Probably the best way to think about a typical Instruct-inspired “chat bot” session is of them sampling from a distribution with a KL-style adjacency to the training corpus (sidebar: this is why shops that do and don’t train/tune on MMLU get ranked so differently than e.g. the arena rankings) at a response granularity, the same way a diffuser/U-net/de-noising model samples at the image batch (NCHW/NHWC) level.
The corpus is stocked with everything from sci-fi novels with computers arguing their own sentience to tutorials on how to do a tricky anti-derivative step-by-step.
This mental model has adequate explanatory power for anything a public LLM has ever been shown to do, but that only heavily implies it’s what they’re doing.
There is active research into whether there is more going on that is thus far not conclusive to the satisfaction of an unbiased consensus. I personally think that research will eventually show it’s just sampling, but that’s a prediction not consensus science.
They might be doing more, there is some research that represents circumstantial evidence they are doing more.
[1] https://github.com/meta-llama/llama/blob/54c22c0d63a3f3c9e77...
- Asking Meta to stop using the term "open source" for Llama
-
Markov Chains Are the Original Language Models
Predicting subsequent text is pretty much exactly what they do. Lots of very cool engineering that’s a real feat, but at its core it’s argmax(P(token|token,corpus)):
https://github.com/facebookresearch/llama/blob/main/llama/ge...
The engineering feats are up there with anything, but it’s a next token predictor.
-
Meta AI releases Code Llama 70B
https://github.com/facebookresearch/llama/pull/947/
-
Stuff we figured out about AI in 2023
> Instead, it turns out a few hundred lines of Python is genuinely enough to train a basic version!
actually its not just a basic version. Llama 1/2's model.py is 500 lines: https://github.com/facebookresearch/llama/blob/main/llama/mo...
Mistral (is rumored to have) forked llama and is 369 lines: https://github.com/mistralai/mistral-src/blob/main/mistral/m...
and both of these are SOTA open source models.
-
[D] What is a good way to maintain code readability and code quality while scaling up complexity in libraries like Hugging Face?
In transformers, they tried really hard to have a single function or method to deal with both self and cross attention mechanisms, masking, positional and relative encodings, interpolation etc. While it allows a user to use the same function/method for any model, it has led to severe parameter bloat. Just compare the original implementation of llama by FAIR with the implementation by HF to get an idea.
What are some alternatives?
stable-diffusion-webui - Stable Diffusion web UI
langchain - ⚡ Building applications with LLMs through composability ⚡ [Moved to: https://github.com/langchain-ai/langchain]
stable-diffusion-webui-amdgpu - Stable Diffusion web UI
text-generation-webui - A Gradio web UI for Large Language Models. Supports transformers, GPTQ, AWQ, EXL2, llama.cpp (GGUF), Llama models.
automatic - SD.Next: Advanced Implementation of Stable Diffusion and other Diffusion-based generative image models
chatgpt-vscode - A VSCode extension that allows you to use ChatGPT
xformers - Hackable and optimized Transformers building blocks, supporting a composable construction.
DeepSpeed - DeepSpeed is a deep learning optimization library that makes distributed training and inference easy, efficient, and effective.
AMD-Stable-Diffusion-ONNX-FP16 - Example code and documentation on how to get FP16 models running with ONNX on AMD GPUs [Moved to: https://github.com/Amblyopius/Stable-Diffusion-ONNX-FP16]
ollama - Get up and running with Llama 3, Mistral, Gemma, and other large language models.
ComfyUI - The most powerful and modular stable diffusion GUI, api and backend with a graph/nodes interface.
transformers - 🤗 Transformers: State-of-the-art Machine Learning for Pytorch, TensorFlow, and JAX.