Upgraded to "major" now. How am I supposed to get any work done!
Refactoring time! Time to see how that code you copied and pasted actually works
Major outages across ChatGPT and API
191–200 of 617 posts
Re: Major outages across ChatGPT and API
#192Re: Major outages across ChatGPT and API
#193I noticed the outage. It feels like a lot of people use it like training wheels on a bicycle until they forget how to ride without it.
Re: Major outages across ChatGPT and API
#194Earlier quoted context omitted.
We were able to failover to Anthropic pretty quickly so limited impact. It'll be harder as we use more of the specialized API features in OpenAI like function calling or now tools...
What’s your use case? The difference in behavior between the two models seems like it would make failover difficult.
It's really not that different - customers can ask questions about conversations, phone, text, video and typically use that to better understand topics, conversions, sales ops, customer service etc...
Re: Major outages across ChatGPT and API
#195Phind is pretty good for coding (LLama 2 trained on billions of extra code tokens) and is still up https://www.phind.com/s
I had great results with Phind. Their newest fine tune model (V7) has been a pleasant experience and better than most open source models out there. Nit: your link has a trailing "s" which makes it 404 :)
Me too. For past few weeks, I had been working on my AHK scripting with Phind. It produced working code consistently and provided excellent command line for various software.
Also I use it for LaTeX, too. It is very helpful providing various package than trying to hunt more information through Google. I got a working tex file within 15 min than it took me 3 weeks 5 years ago!
Re: Major outages across ChatGPT and API
#196https://github.com/XueFuzhao/OpenMoE
Check out this open source Mixture of Experts research. Could help a lot with performance of open source models.
Re: Major outages across ChatGPT and API
#197Lots of jokes to be made, but we are setting ourselves up for some big rippling negative effects by so quickly building a reliance on providers like OpenAI. It took years before most companies who now use cloud providers to trust and be willing to bet their operations on them. That gave the cloud providers time to make their systems more robust, and to learn how to resolve issues quickly.
Provided we can keep riding this hype wave for a while, I think the logical long term solution is most teams will have an in house/alternative LLM they can use as temporary backup. Right now everyone is scrambling to just get some basic products out using LLMs but as people have more breathing room I can't image most teams not having a non-OpenAI LLM that they are using to run experiments on. At the end of the day, O…
Except that it is currently impossible to replace GPT-4 with an open model.
Re: Major outages across ChatGPT and API
#198Earlier quoted context omitted.
I say this as a huge fan of GPT, but it's amazing to me how terrible of a company OpenAI is and how quickly we've all latched onto their absolutely terrible platform. I had a bug that wouldn't let me login to my work OpenAI account at my new job 9 months ago. It took them 6 months to respond to my support request and they gave me a generic copy/paste answer that had nothing to do with my problem. We spend tons and to…
I've personally never scaled a B2B&C company from 0 to over 1 billion users in less than a year, but I do feel like it's probably pretty hard. Especially setting up something like a good support organization in a time of massive labor shortages seems like it would be pretty tough. I know they have money, but money isn't a magic wand for creating people. They could've also kept it a limited beta for much longer, but t…
I wonder if they spend time trying to do support via GPT4 itself.
Re: Major outages across ChatGPT and API
#199Might as well have a quick discussion here. How's everyone finding the new models? 4-Turbo is a bit worse than 4 for my NLP work. But it's so much cheaper that I'll probably move every pipeline to using that. Depending on the exact problem it can even be comparable in quality/price to 3.5-turbo. However the fact that output tokens are limited to 4096 is a big asterisk on the 128k context.
Here we go with these “it looks worse” just like a month back when people feel it it was worse
It's probably a smaller, updated (distilled?) version of gpt-4 model given the price decrease, speed increase, and turbo name. Why wouldn't you expect it to be slightly worse? We saw the same thing with 3-davinci and 3.5-turbo.
I'm not going off pure feelings either. I have benchmarks in place comparing pipeline outputs to ground truth. But like I said, it's comparable enough to 4, at a much lower price, making it a great model.
Edit: After the outage, the outputs are better wtf. Nvm it has some variance even at temp = 0. I should use a fixed seed.
Re: Major outages across ChatGPT and API
#200Lots of jokes to be made, but we are setting ourselves up for some big rippling negative effects by so quickly building a reliance on providers like OpenAI. It took years before most companies who now use cloud providers to trust and be willing to bet their operations on them. That gave the cloud providers time to make their systems more robust, and to learn how to resolve issues quickly.
> we are setting ourselves up for some big rippling negative effects by so quickly building a reliance on providers like OpenAI. You said it so well!
It's possible to include API gateways and API Proxies in between calls to normalize them across multiple providers as they become available.