LocalAI
LocalAI copied to clipboard
mudler
fix(llama.cpp): disable mirostat as default
Even if increasing the quality of the output, it has shown to have performance drawbacks to be so noticeable that the confuses users about speed of LocalAI ( see also https://github.com/mudler/LocalAI/issues/2780 ). This changeset disables Mirostat by default (which can be still enabled manually).
Deploy Preview for localai ready!
| Name | Link |
|---|---|
| Latest commit | c6806227429266ad5c0a754270a33fc173abd8be |
| Latest deploy log | https://app.netlify.com/sites/localai/deploys/6698f00126e5d40008ebdefd |
| Deploy Preview | https://deploy-preview-2911--localai.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Deploy Preview for localai ready!
| Name | Link |
|---|---|
| Latest commit | ec9855770367e5f90b33f67c5963e9eef8957df1 |
| Latest deploy log | https://app.netlify.com/sites/localai/deploys/67a4f32f0383480008e28a66 |
| Deploy Preview | https://deploy-preview-2911--localai.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
This PR diff shows a change in the backend_config.go file in the core/config package. The file defines the BackendConfig struct which holds configuration options for a backend.
The change is in the line where the defaultMirostat variable is defined. The comment at the beginning of the line indicates that the change is related to an issue on the GitHub repository, namely issue #2780.
Before the change, the defaultMirostat variable was set to 2. After the change, it is set to 0. This change might be a result of resolving the aforementioned issue, which would have required adjusting the default value of the mirostat configuration option.
The mirostat configuration option might be related to the Mirostat algorithm used in the LocalAI system. The change suggests that the default value of mirostat has been set to 0, which means that the Mirostat algorithm might be disabled or not used by default in the system.
Overall, the change seems to be a configuration update to address an issue and possibly disable or change the behavior of the Mirostat algorithm in the LocalAI system.
the failing test-linux run was acting strange and was unable to be restarted... auto-merge will kick off a fresh cycle.
