Earlier quoted context omitted.
What works for me to avoid these problems is not scaling.
That approach doesn’t scale though.
Not with that attitude it doesn’t!
Claude outage – Resolved
161–167 of 167 posts
Re: Claude outage – Resolved
#162Earlier quoted context omitted.
It's been a while since I messed with serious hardware, what's the cooling noise level? I guess they have to be water cooled or the rack format 8u ones would be about 100db
My 4x 15k rpm 1U fans I use to cool my twin AMD V620s make a horrible racket, especially how they resonate with the rest of the workstation's case fans. Similar in volume and annoyance to running an 8" circular saw. I can only imagine it would probably be as bad or worse than that.
Yeah my experience in the past was that datacenter hardware (air cooled, at least, I've never dealt with water cooled) uses tiny fans at or about 15000RPM, so it matches basically what you're saying or worse.
I always loved this video: https://www.youtube.com/watch?v=tDacjrSCeq4
Re: Claude outage – Resolved
#163Earlier quoted context omitted.
My 4x 15k rpm 1U fans I use to cool my twin AMD V620s make a horrible racket, especially how they resonate with the rest of the workstation's case fans. Similar in volume and annoyance to running an 8" circular saw. I can only imagine it would probably be as bad or worse than that.
Yeah my experience in the past was that datacenter hardware (air cooled, at least, I've never dealt with water cooled) uses tiny fans at or about 15000RPM, so it matches basically what you're saying or worse. I always loved this video: https://www.youtube.com/watch?v=tDacjrSCeq4
That was one of those fantastic early google videos/youtube things I probably watched 100 times. This was another from (roughly) that era: https://www.youtube.com/watch?v=ULSA5wktywI
Re: Claude outage – Resolved
#164Earlier quoted context omitted.
The other bizarre word I've now noticed and can't understand is "pathological". As in "bug has turned pathological"
In old school ML a pathological solution is often a collapse of some kind due to an underspecified objective. Maybe one parameter explodes or the model predicts "0" for everything I read this as "the code is working as intended but the bug is an artifact of the original design"
I genuinely have no idea what it is meant to mean in the context it uses it. Load-bearing etc is annoying but roughly understandable, some of the opus5 classics are completely out there.
I'm a native English speaker as well, I shudder to think what a second language speaker would do (even if they were very confident with the language!).
Re: Claude outage – Resolved
#165It goes down so often that I've advocated my company create enterprise Codex accounts as backup for devs.
Using the backup compute capacity stored above their shoulders is somehow unthinkable?
Why do you think we don't use our brains when we use Claude Code?
Arguably, my brain usage is higher when using Claude Code. It's just used in a different way.
Re: Claude outage – Resolved
#166Earlier quoted context omitted.
Using the backup compute capacity stored above their shoulders is somehow unthinkable?
Why do you think we don't use our brains when we use Claude Code? Arguably, my brain usage is higher when using Claude Code. It's just used in a different way.
This is a straw man argument and perhaps a little bit of projection of your own insecurities, because that is not what I was saying.
Re: Claude outage – Resolved
#167[flagged]