336 karma · joined October 11, 2021
And there's a hard place that everyone freaks out at API prices and on-demand Opex models outside of a niche (I use API for personal research for quite focused queries and slightly more reassurance on being the customer and not the product) but this is very competitive + not sticky.
The other route for fast S3 writes others have used (Turso springs to mind) is express S3 zones but those have a lot of region specific fine print still.
> It’s not as simple as writing data straight to S3. Lots of PUTs for tiny blobs of data are slow and expensive. Instead, we use an SSD tier to optimize speed and cost:
> When you write data to an actor’s SQLite database, the write is acknowledged once SSDs in 2 of 3 availability zones have it. Then, the data is batched to S3 in the background. This means that S3 is never on the write path, which lowers latency and cost. When reading data or waking an actor, Rivet reads from SSDs if already cached and falls back to S3 if not. SSD caches can be tuned to meet your needs, giving you configurable tiered storage for your actors.
In seriousness this is an example of the previous point. Rather than engaging with the issue the tech/DC industry seems to think they can wordplay their way out of it by quibbling about irrelevant technical details and people are primed to get extremely angry at grinfucking type behaviour nowadays.
Well that’s the point. They’re not continuing at that rate of growth.
> I predict that eventually the training expenditure is going to slow down. At that point, the large commercial providers are likely hoping they can keep inference demand up, and recoup their investment.
The big labs can't do this that's their edge over open models. The stickiness is critical for them to keep up. They might try again but it's going to finish badly.
It can't be both "so easy and hands free anyone can use it" and also "well they must be using the wrong model/holding it wrong if it's not working for them". If there weren't tradeoffs of the different models then it wouldn't be exposed to the user.
There just isn’t a sane way to look at this as “investment”
AnthropenAI are the ones driving a lot of that infrastructure spending when they’re such big consumers of compute but they’re not the ones feeling the brunt of the infra spending. Although those costs will bubble up to them indirectly eventually.