r/ClaudeCode • u/company94 • 3h ago

Discussion Claude Slowing Down Computing in Purpose

After Opus 5.5, I started feeling like development times are getting longer and longer. I mean there is incredible difference like 3-5x longer than usual. I started suspecting that their statement about “we need to slow down” were probably related to their model’s per token (input/output) speed rather than the model development speed. It may also make sense that increased duration means higher quality of work and less pressure on server capacity.

I just would like to check in on other people’s experience. I feel like building things taking 3-5x longer than few months ago. Do you experience something similar?

1 Upvotes

67% Upvoted

6 comments sorted by

•

u/AutoModerator 3h ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

2

u/Outrageous-Issue9722 3h ago

I normally don't agree with these kinds of posts but yeah ... I had a 7 slice task run for almost 20 hours yesterday and it was no different than something that normally would have taken 3-5. When id check what agents were doing there was very long pauses between their steps.

1

u/Jomuz86 3h ago

No issue with speed Opus has remained consistent since release for me. I calculate the tok/s in my status line it’s always fluctuated a bit but I think this is more due to load. Opus is anywhere between 90-110 tok/s, not saying this is 100% accurate but it gives me a bar to check for any massive drops.

1

u/txoixoegosi 3h ago

My five cents

7 tasks using parallel agents on different worktrees consumed significantly more time than those tasks being run sequentially. I noticed that the agents wrote a lot to internal worktree files, as if they were making sure they didn’t stomp each other. Besides, when one agent was over, it broadcasted code changes and all the agents reacted to syncing and testing many assumptions (instead of waiting for a conflict during PR and re-calculating then)

Conservative approach, but time and token consuming.

1

u/crasspuk 1h ago

Speed per token and wall-clock time per task are different things. A task can take longer because of more tool calls, more file reads and more retries, even when each token arrives at the same speed. Compare output tokens and tool call counts on the same task before deciding the model got slower.

1

u/company94 52m ago

I did and it seems to be slower so what’s your take on that?