News for hackers. Stuff that matters.
Re:Kimi-K3 Technical Report [pdf] by GodelNumbering on Monday July 27, 2026 @12:59PM (#49072456)
> And hire 2 or 3 dev ops to keep it running

Not a devops but I'd say one full time is already too many.

Re:Kimi-K3 Technical Report [pdf] by dboreham on Monday July 27, 2026 @01:10PM (#49072619)
Yes but zero is not enough and where do you get a fraction of a competent dev op from?
Re:Kimi-K3 Technical Report [pdf] by layer8 on Monday July 27, 2026 @01:15PM (#49072700)
From the other dev-op work you’re doing.
Re:Kimi-K3 Technical Report [pdf] by JacobAsmuth on Monday July 27, 2026 @04:02PM (#49074850)
Now you're thinking like management!
Re:Kimi-K3 Technical Report [pdf] by ayewo on Monday July 27, 2026 @01:50PM (#49073186)
Understood but sharing your existing devops resources with this will soon become a bottleneck especially when any major downtime will keep several engineers (and long-running agents) blocked from any meaningful work until availability improves.
Re:Kimi-K3 Technical Report [pdf] by layer8 on Monday July 27, 2026 @02:08PM (#49073411)
Not my experience, from an SMB that maintains its own hardware and services. You have a certain contingent of competent engineers who distribute their work across projects, and it generally works out fine. Or course you plan with some redundancy and fall-back plans in your systems.
Re:Kimi-K3 Technical Report [pdf] by ayewo on Monday July 27, 2026 @04:11PM (#49074940)
The top poster mentioned LLM spend of millions/month to justify the estimated capex of $6m to self-host Kimi on own infra.

Add to this number another $1.5m/yr in opex, so not sure I’d call such an enterprise wealthy enough to spend those kinds of sums on LLMs an “SMB”.

Re:Kimi-K3 Technical Report [pdf] by twobitshifter on Monday July 27, 2026 @07:28PM (#49077005)
colocate and split the cost with others.