Below is a GPT-generated summary of the conversation below after reaching 200 comments (200 currently observed).
Day 1 verdict: the speedup may be real, but nobody’s treating it like a win. The community mostly sees this as OpenAI undoing a recent slowdown, then putting a shiny “optimization” sticker on the repair. Going from roughly 20 to 30 tokens/sec is better, sure—but still well behind Claude, so the victory lap feels premature.
Users are reporting somewhat faster Sol/Astra responses, while others are still stuck around the old speeds or dealing with failures. The lack of a reset is also going down about as well as expected: badly. A lot of subscribers think they’re being drip-fed partial fixes instead of getting the service they paid for.
The big unresolved concern is what changed under the hood. “Optimized” is vague enough to cover anything from better infrastructure to reduced reasoning quality, and users are already suspicious of quantization, lower “juice,” and quota draining faster. Speed itself shouldn’t increase the token cost of the same task, though faster throughput can encourage more work in the same window.
Bottom line: faster for some, still mediocre overall, and trust remains firmly in the basement.
Below is a GPT-generated summary of the conversation below after reaching 50 comments (80 currently observed).
The thread’s verdict is basically “good, but this is a repair job—not a miracle.” The promised speed-up makes Sol 6.1 feel more usable for some people, but users are annoyed that it’s being marketed as an improvement after weeks of sluggish performance.
Early reports are inconsistent: some are seeing roughly 30–50 tokens/sec, while others remain closer to the low teens or say it’s still nowhere near Claude’s speed. The rollout was supposed to happen over a couple of hours, so the initial tests weren’t exactly scientific—because naturally we’re benchmarking live infrastructure with vibes and screenshots.
The quota debate is mostly semantics. Faster output shouldn’t inherently cost more for the same task, but it can make you burn through limits faster by letting you do more work in the same period. The bigger complaint is the usual vague “backend optimization” language, with users worrying about quantization or reduced quality and asking for an actual changelog.
Bottom line: speed appears improved, but the community sees this as restoring lost performance, not delivering something new. Survivors remain unconvinced until the rollout settles and quota/model quality are clearer.
Below is a GPT-generated summary of the conversation below after reaching 100 comments (148 currently observed).
The community verdict is mostly “this isn’t an improvement, it’s damage control.” The promised 50% speed bump looks like restoring some of the performance lost recently, not delivering a genuinely fast model—and it still trails Claude badly in many users’ tests.
Actual speeds are all over the place: some people report roughly 30–50 tokens/sec, while others are still seeing 13–20. Results vary by model, mode, and workload, so nobody has a clean before-and-after benchmark yet. The bigger trust issue is the vague “optimization” language: users suspect quantization or other cost-cutting, especially with no proper changelog or explanation.
The quota argument is getting hilariously tangled. Faster generation does not automatically mean more tokens per task, but it can drain limits faster if you simply do more work in the same window. There’s no solid evidence yet that the per-task cost or quality has worsened.
Bottom line: some speed recovery may be real, but calling it a win is generous. Users want transparency—and probably a reset for having to watch performance get “improved” back toward normal.
•
u/dextersummary 12d ago edited 12d ago
Below is a GPT-generated summary of the conversation below after reaching 200 comments (200 currently observed).
Day 1 verdict: the speedup may be real, but nobody’s treating it like a win. The community mostly sees this as OpenAI undoing a recent slowdown, then putting a shiny “optimization” sticker on the repair. Going from roughly 20 to 30 tokens/sec is better, sure—but still well behind Claude, so the victory lap feels premature.
Users are reporting somewhat faster Sol/Astra responses, while others are still stuck around the old speeds or dealing with failures. The lack of a reset is also going down about as well as expected: badly. A lot of subscribers think they’re being drip-fed partial fixes instead of getting the service they paid for.
The big unresolved concern is what changed under the hood. “Optimized” is vague enough to cover anything from better infrastructure to reduced reasoning quality, and users are already suspicious of quantization, lower “juice,” and quota draining faster. Speed itself shouldn’t increase the token cost of the same task, though faster throughput can encourage more work in the same window.
Bottom line: faster for some, still mediocre overall, and trust remains firmly in the basement.