Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GPT-5.2 and GPT-5.2-Codex are now 40% faster

twitter.com

Post reply on HN
Print view View original

51–58 of 58 posts

Re: GPT-5.2 and GPT-5.2-Codex are now 40% faster

#51

Post by quinncom »

tedsanders wrote: post #45
deaux wrote: post #20

Earlier quoted context omitted.

It looks like you do pull shenanigans like these [0]. The person you're replying to even mentioned "ChatGPT 5.2", but you're specifically talking only about the API, while making it sound like it applies across the board. Also appreciate the attempt to further hide this degradation of the product they paid for from users by blocking the prompt used to figure this out. Happy to retract if you can state [0] is false. […

Yes, independent of the API speedup, we also recently reduced the thinking effort in ChatGPT. Our intent here was purely user experience, not cost savings. People have complained about the slow speeds of the Thinking models for a long time (myself included), so we recently retuned it to be faster, at the expense of less thoroughness. I won't BS you that costs are never part of our decision making. If costs didn't mat…

I’m so disappointed by this. It’s immediately noticeable that the results for the types of queries I make are worse. Queries using 5.2 Thinking now return very quickly, but with noticeably worse results.

Re: GPT-5.2 and GPT-5.2-Codex are now 40% faster

#52

Post by [deleted] »

tedsanders wrote: post #45
deaux wrote: post #20

Earlier quoted context omitted.

It looks like you do pull shenanigans like these [0]. The person you're replying to even mentioned "ChatGPT 5.2", but you're specifically talking only about the API, while making it sound like it applies across the board. Also appreciate the attempt to further hide this degradation of the product they paid for from users by blocking the prompt used to figure this out. Happy to retract if you can state [0] is false. […

Yes, independent of the API speedup, we also recently reduced the thinking effort in ChatGPT. Our intent here was purely user experience, not cost savings. People have complained about the slow speeds of the Thinking models for a long time (myself included), so we recently retuned it to be faster, at the expense of less thoroughness. I won't BS you that costs are never part of our decision making. If costs didn't mat…

[deleted]

Re: GPT-5.2 and GPT-5.2-Codex are now 40% faster

#54

Post by tedsanders »

quinncom wrote: post #51
tedsanders wrote: post #45

Earlier quoted context omitted.

Yes, independent of the API speedup, we also recently reduced the thinking effort in ChatGPT. Our intent here was purely user experience, not cost savings. People have complained about the slow speeds of the Thinking models for a long time (myself included), so we recently retuned it to be faster, at the expense of less thoroughness. I won't BS you that costs are never part of our decision making. If costs didn't mat…

I’m so disappointed by this. It’s immediately noticeable that the results for the types of queries I make are worse. Queries using 5.2 Thinking now return very quickly, but with noticeably worse results.

It's unfortunately hard to make everyone happy. For now we're going to keep the default where it is, but we'll bump extended back up so that people can still get longer reasoning when they want it.

Re: GPT-5.2 and GPT-5.2-Codex are now 40% faster

#55

Post by offnominal »

tedsanders wrote: post #45
deaux wrote: post #20

Earlier quoted context omitted.

It looks like you do pull shenanigans like these [0]. The person you're replying to even mentioned "ChatGPT 5.2", but you're specifically talking only about the API, while making it sound like it applies across the board. Also appreciate the attempt to further hide this degradation of the product they paid for from users by blocking the prompt used to figure this out. Happy to retract if you can state [0] is false. […

Yes, independent of the API speedup, we also recently reduced the thinking effort in ChatGPT. Our intent here was purely user experience, not cost savings. People have complained about the slow speeds of the Thinking models for a long time (myself included), so we recently retuned it to be faster, at the expense of less thoroughness. I won't BS you that costs are never part of our decision making. If costs didn't mat…

Did they reduce thinking effort on Codex too? It seems to have become significantly worse in the past couple of days. It keeps making dumb mistakes (that it wouldn't earlier), so my chats are much longer to get it to fix them. That might be more expensive for OpenAI (and me!).

Re: GPT-5.2 and GPT-5.2-Codex are now 40% faster

#56

Post by wahnfrieden »

walletdrainer wrote: post #37
wahnfrieden wrote: post #13

Earlier quoted context omitted.

this is for api only

Is it even possible to actually use codex any other way? Every time I’ve tried logging in instead of using the API, I’ve hit the usage limits within a couple of hours.

Yes with Pro tier sub.

Re: GPT-5.2 and GPT-5.2-Codex are now 40% faster

#57

Post by benterix »

OutOfHere wrote: post #9

OpenAI in my estimation has the habit of dropping a model's quality after its introduction. I definitely recall the web ChatGPT 5.2 being a lot better when it was introduced. A week or two later, its quality suddenly dropped. The initial high looked to be to throw off journalists and benchmarks. As such, nothing that OpenAI says in terms of model speed can be trusted. All they have to do is lower the reasoning effort…

> I hope I am wrong, because if I am right, it's a con game.

I don't think they perceive it as a con game, on the contrary. They say below: "we also recently reduced the thinking effort in ChatGPT. Our intent here was purely user experience, not cost savings."

They are not the only ones playing this game. Google did the same with Gemini Pro.

Re: GPT-5.2 and GPT-5.2-Codex are now 40% faster

#58

Post by pickleRick243 »

tedsanders wrote: post #54
quinncom wrote: post #51

Earlier quoted context omitted.

I’m so disappointed by this. It’s immediately noticeable that the results for the types of queries I make are worse. Queries using 5.2 Thinking now return very quickly, but with noticeably worse results.

It's unfortunately hard to make everyone happy. For now we're going to keep the default where it is, but we'll bump extended back up so that people can still get longer reasoning when they want it.

This makes no sense. Why lower extended thinking time? Those who want faster answers can just use standard. The only purpose this serves is to "trick" the user into thinking he's still receiving "extended thinking" level answers at faster speed.
Post reply on HN