797891c995
* Initial Library Loader * Load library as part of Model factory * Dynamically search and find the dlls * Update tests to use locally built runtimes * Fix dylib loading, add macos runtime support for sample/tests * Bypass automatic loading by default. * Only set CMAKE_OSX_ARCHITECTURES if not already set, allow cross-compile * Switch Loading again * Update build scripts for mac/linux * Update bindings to support newest breaking changes * Fix build * Use llmodel for Windows * Actually, it does need to be libllmodel * Name * Remove TFMs, bypass loading by default * Fix script * Delete mac script --------- Co-authored-by: Tim Miller <innerlogic4321@ghmail.com> |
||
|---|---|---|
| .. | ||
| gptj | ||
| llama | ||
| llama.cpp-230511@03ceb39c1e | ||
| llama.cpp-230519@5ea4339273 | ||
| llama.cpp-mainline@37bdb72c4f | ||
| scripts | ||
| CMakeLists.txt | ||
| dlhandle.h | ||
| gptj_impl.h | ||
| gptj.cpp | ||
| llama.cpp.cmake | ||
| llamamodel_impl.h | ||
| llamamodel.cpp | ||
| llmodel_c.cpp | ||
| llmodel_c.h | ||
| llmodel_shared.cpp | ||
| llmodel.cpp | ||
| llmodel.h | ||
| mpt_impl.h | ||
| mpt.cpp | ||
| README.md | ||
| replit_impl.h | ||
| replit.cpp | ||
| utils.cpp | ||
| utils.h | ||
GPT4ALL Backend
This directory contains the C/C++ model backend used by GPT4All for inference on the CPU. This backend acts as a universal library/wrapper for all models that the GPT4All ecosystem supports. Language bindings are built on top of this universal library. The native GPT4all Chat application directly uses this library for all inference.
What models are supported by the GPT4All ecosystem?
Currently, there are three different model architectures that are supported:
- GPTJ - Based off of the GPT-J architecture with examples found here
- LLAMA - Based off of the LLAMA architecture with examples found here
- MPT - Based off of Mosaic ML's MPT architecture with examples found here
Why so many different architectures? What differentiates them?
One of the major differences is license. Currently, the LLAMA based models are subject to a non-commercial license, whereas the GPTJ and MPT base models allow commercial usage. In the early advent of the recent explosion of activity in open source local models, the llama models have generally been seen as performing better, but that is changing quickly. Every week - even every day! - new models are released with some of the GPTJ and MPT models competitive in performance/quality with LLAMA. What's more, there are some very nice architectural innovations with the MPT models that could lead to new performance/quality gains.
How does GPT4All make these models available for CPU inference?
By leveraging the ggml library written by Georgi Gerganov and a growing community of developers. There are currently multiple different versions of this library. The original github repo can be found here, but the developer of the library has also created a LLAMA based version here. Currently, this backend is using the latter as a submodule.
Does that mean GPT4All is compatible with all llama.cpp models and vice versa?
Unfortunately, no for three reasons:
- The upstream llama.cpp project has introduced a compatibility breaking re-quantization method recently. This is a breaking change that renders all previous models (including the ones that GPT4All uses) inoperative with newer versions of llama.cpp since that change.
- The GPT4All backend has the llama.cpp submodule specifically pinned to a version prior to this breaking change.
- The GPT4All backend currently supports MPT based models as an added feature. Neither llama.cpp nor the original ggml repo support this architecture as of this writing, however efforts are underway to make MPT available in the ggml repo which you can follow here.
What is being done to make them more compatible?
A few things. Number one, we are maintaining compatibility with our current model zoo by way of the submodule pinning. However, we are also exploring how we can update to newer versions of llama.cpp without breaking our current models. This might involve an additional magic header check or it could possibly involve keeping the currently pinned submodule and also adding a new submodule with later changes and differienting them with namespaces or some other manner. Investigations continue.
What about GPU inference?
In newer versions of llama.cpp, there has been some added support for NVIDIA GPU's for inference. We're investigating how to incorporate this into our downloadable installers.
Ok, so bottom line... how do I make my model on Hugging Face compatible with GPT4All ecosystem right now?
- Check to make sure the Hugging Face model is available in one of our three supported architectures
- If it is, then you can use the conversion script inside of our pinned llama.cpp submodule for GPTJ and LLAMA based models
- Or if your model is an MPT model you can use the conversion script located directly in this backend directory under the scripts subdirectory