GPTCache: Slash Your LLM API Costs by 10x
1–7 of 7 posts
Re: GPTCache: Slash Your LLM API Costs by 10x
#2If you're leveraging LLMs for your projects, it's definitely worth giving GPTCache a look!
Re: GPTCache: Slash Your LLM API Costs by 10x
#3As most ML is inherently probabilistic, it seems reasonable to make an LLM cache both semantic and _stochastic_, i.e. you wouldn't want the same answer every time you use "pick me a color" as prompt. Injecting the original LLM (GPT, Bard, etc) response as prompt for alpaca or some other model could make this cache virtually invisible.
Re: GPTCache: Slash Your LLM API Costs by 10x
#4Re: GPTCache: Slash Your LLM API Costs by 10x
#5Keep up the awesome work. I've run across this problem myself - I somehow used $20 just testing a small demo I made with GPT-3.5. As most ML is inherently probabilistic, it seems reasonable to make an LLM cache both semantic and _stochastic_, i.e. you wouldn't want the same answer every time you use "pick me a color" as prompt. Injecting the original LLM (GPT, Bard, etc) response as prompt for alpaca or some other mo…
Re: GPTCache: Slash Your LLM API Costs by 10x
#6Between langchain and this it looks like every new LLM API wrapper startup is going to use python.
Re: GPTCache: Slash Your LLM API Costs by 10x
#7Between langchain and this it looks like every new LLM API wrapper startup is going to use python.
It's true that Python seems to be the go-to language for many LLM API wrapper projects. Its popularity in the AI and ML communities might be a contributing factor.
Not to mention the chatgpt code interpreter plugin allowing sandboxed python execution and many beginners starting to code with llms, nearly everything will be in python eventually.