jamesblonde

This just confirms to me that the devs who are furthest from users (platform and security folks) are still in denial about AI for coding. The idea that they continue to react to security and privacy threats by relying on hand-crafted code is ostrich-like denial of the reality of daily security breaches at much larger, better resourced companies.

AI is a tool - like a compiler or a pen-testing tool or maybe like an uber-tool that can do all those things and more. It's not hard. 24 hours - put your best pentester against GLM-5.3 abliterated (host locally, so there's no data leakage to LLM providers). You know who will win and it won't even be close.

This is the beginning of a flight to perceived quality in all things digital and monetary. Fear of losing your money is among the most potent basal human instincts.

I have access to a server with 4 x h200 cards - 540 GB in total memory, but it appears I have to go to 4bit or 3bit even to serve it. Any idea if that is feasible/desirable (we have restrictions that we can't use a chinese model!).

Is this Germany - is there a subsidy included here?

Git was designed with assumptions about local file storage which make it challenge when storing data in a distributed file system. We built our distributed filesystem, HopsFS, to store data in S3. To support high performance git in FUSE, our writes hit remote NVMe disk(s) and asynchronously sync to S3 (you can replicate on NVMes or just do failure recovery). Previously, we used remote NVMe disks as a write-through cache, but that doesn't work with git, S3 latency is too high.

That was my point - it needs to invest its capital in Europe. That will solve its ails.

As Rutger Bergman says about inequality: "it's taxes, taxes, taxes..."

For Europe, it's "capital, capital, capital".

In 2015, MySQL Cluster (NDB Cluster engine) benchmarked 200m transactions/second on commodity hardware [ref]. It was read-committed transactions, not snapshot isolation, but still impressive. NDB has now become RonDB, but is still based on a non-blocking 2-phase commit protocol and is GPL-v2.

RonDB now has support for infiniband, so ought to blow through the 1B ops/sec. For reference, that is 1 GHz of transactions/sec.

[ref] https://www.slideshare.net/frazerClement/200-million-qps-on-...

DuckDB's sweet spot is for 'smallish' lakehouses. So, ingestion should not be via duckdb, but rather something like Python/DLTHub for small scale or Spark for large scale or Kafka/Debezium/Flink for streaming data.

For the full weights, unoptimized on vLLM with 2 Nvidia 6000 RTX 48GBs connected by NVLink, i only get 14 tokens/sec with open-code. For batched operations, it climbs to 55 tokens/sec.

For FP8, on a single Nvidia 6000 RTX 48GB, i get 13 tokens/sec on a single GPU and 46 tokens/sec batched.

Sodium-ion batteries are only starting, their price floor in a few years will make solar energy unmatched in price for energy production.

This is the first proof point that the technology is viable - a customer is stumping up big cash.

Fifa is a reflection of the world. All members (nations) get a vote. Most countries are corrupt. Thank go there is still a bastion of democracy/fairness left in Uefa.

Yes, coding agents have reduced the skills/knowledge required to operate workloads on virtualized hardware. K8S and its ecosystem has changed so that it now provides 90% of what you need from the public cloud providers. Big changes that make 8-15X savings by running your own workloads. I think it will be the big players who move first, as they have most to save and have the resources to make it happen.

It certainly feels like Netflix is now a k8s shop. And it probably only a matter of time until they start repatriating workloads to optimize for costs. Then the world will sit up and notice.

It took me 5 years to get the boat - a 22ft daycruiser with toilet. That was 15 years ago, haven't looked back. Got a daycruiser from the UK. Drove there, bought a trailer there, drove it home. Arbitrage during the financial crisis - half the price of the same boat in Sweden at the time.