-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate Swap to GPT-4 #47
Comments
Worth investigating & keeping an eye on this but main issue before was latency. Again, if we have a good baseline then we can compare quality of generated output. |
I've used the new prompt-eng tooling I wrote to create a google sheet of answers comparing gpt-3.5-turbo to gpt-4. Imo the difference is so great that we have no choice but to switch, assuming the cost isn't prohibitively. I'm curious to know what others think |
I've created a benchmark to compare outputs from gpt-3.5-turbo-16k to gpt-4. We'll need a handful of people to go through and rank their preferences. |
This is related to #34 so I'm going to close this as a duplicate. |
With falling API prices and rising importance of this project, I suspect this might now be possible. We should find the exact API costs of a message back and forth, work out some projected usage figures, and talk with Plex to see if it fits the org's budget.
The text was updated successfully, but these errors were encountered: