
Data and distributed systems. RT is not endorsement // board game maker @plai_cards // Wine connoisseurs? try https://teapawt.net/t.co/DLc65ap5E1
Joined May 2016
- Tweets2.2K
- Following746
- Followers124
- Likes1.5K
MartSec retweeted
My advice for software engineers in 2026
Get into formal methods
Not to prove your system correct but to prove your thinking correct
MartSec retweeted
Ahir les floristeries de la plaça de Catalunya es van rebentar al crit de "Pedro Sánchez, hijo de puta". Ahir van passar moltes coses, però això també. I ho vaig observar de ben aprop.
MartSec retweeted
Vosaltres sou molt joves i potser no sabreu que la primera càmera de videovigilància policial als carrers de Barcelona es va instal·lar el 2001, amb Joan Clos d'alcalde, a la plaça de George Orwell, al barri Gòtic.
MartSec retweeted
The NSA is telling American companies to take production systems offline. The AI-era of cybersecurity has fully arrived.
Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.
MartSec retweeted
Top 10 practical resources to learn databases (for people who ship code + get paged):
1) Designing Data-Intensive Applications (book)
Great mental models: replication, partitioning, indexes, transactions, tradeoffs.
2) Database Internals by Alex Petrov (book)
LSM vs B-tree, WAL, compaction, caching. Makes performance incidents less mysterious.
3) Postgres docs (especially EXPLAIN, indexes, VACUUM, isolation)
If you run Postgres in prod, this is higher ROI than most courses.
4) Use The Index, Luke! (site)
Concrete examples of why your query is slow and how indexes actually get used.
5) CMU 15-445/645 Database Systems (free lectures + projects)
Real systems thinking: storage engines, concurrency control, recovery.
6) Martin Kleppmann’s talks (YouTube)
Clear explanations of consistency, consensus, stream processing, and real failure modes.
7) Andy Pavlo’s database videos (YouTube)
Practical tuning stories: why your p99 blows up, what the planner is doing, what not to do.
8) PG exercises + LeetCode SQL (practice)
Good for muscle memory: joins, windows, grouping, NULL weirdness, edge cases.
9) Build a tiny DB project (practice)
Write: B-tree/LSM KV store + WAL + crash recovery + a simple SQL parser. You learn more from the bugs than the happy path.
10) Run a DB like a service (practice)
Spin up Postgres/MySQL, enable slow query logs, add pgbouncer, set backups + restore drills, test failover, track p95/p99 query latency with real dashboards
[generated using my AI agent, hope this was useful]
MartSec retweeted
Third question on AI.
A question that also remains unasked is whether the AI boom can continue without leading to a massive increase in inequality.
A recent paper by Stijn Van Nieuwerburgh runs the numbers on how much revenue the AI industry needs to generate to recover its massive investment (summary and a link to the paper can be found here: brookings.edu/articles/finan…).
Van Nieuwerburgh’s arithmetic should make us more concerned. AI investments will average about 3.6% of GDP annually between 2025 and 2032. Van Nieuwerburgh calculates that, using a 10% rate of return, the industry would need to generate annual revenues of about $3.7 trillion by 2032 to recover these costs (growing from its current levels of about $200 billion or so). That is significantly more than 10% of current US national income, and will likely remain around 10% of national income by 2032, even if GDP growth rose from its current level.
A large fraction of this revenue will go to capital income. That means a massive increase in the share of capital in national income, which has already risen substantially over the last 25 years or so – now standing at an all-time high of about 47% (bls.gov/news.release/pdf/pro…).
Capital income is much more unequally distributed than labor income, so a massive increase in the capital share of national income will translate into a very sizable surge in inequality.
The rise in inequality may not stop with the capital share. My work with Pascual Restrepo documents that (automation-driven) increases in the capital share of national income are typically associated with rising labor income inequality as well (see, for example, economics.mit.edu/sites/defa…). The same may happen in the next several years, boosting inequality further.
What is missing from our current debate is any discussion of a fundamental dilemma these numbers pose: can the AI boom avoid both an economically costly crash and a huge increase in inequality?
If the industry reaches these revenues, inequality surges. If the industry does not become profitable, a crash, with substantial costs in terms of lost output and jobs, becomes likely.
My assessment would be that the industry is unlikely to reach levels of revenue Van Nieuwerburgh calculates. First, diffusion has been and will likely continue to be slow. Second, competition from open-weight models, which are getting better, will limit how much proprietary models can charge. Third, despite important advances, I still believe that AI models will not be able to automate entire occupations anytime soon, thus limiting their value to businesses as cost-saving devices.
Whether this leads to a crash or not is more complicated and will depend on whether various AI companies are bailed out and what kind of support they receive.
Nevertheless, even if revenues fall short of these gargantuan amounts and we avoid a dramatic surge in inequality, I expect that the diffusion of AI will push up inequality between capital and labor and within labor.
If inequality does surge, a further question becomes central: can our democracy survive such astronomical levels of inequality?
MartSec retweeted
🧵L'anàlisi forense sobre l'atac a Adif i Renfe deixa un panorama desolador, segons fonts de la investigació: més de 150 milions de registres robats que inclouen DNIs, adreces i bitllets nominatius.
Just doubled the prompt processing speeds from 539 token/s to 1290 tokens/s.
Qwen3.8-Flash-Next on consumer GPU is now blazing fast.
Next on the list is further optimizations on kernels and swapping which should boost results by 3X-4X.
github.com/Niko1221/Strata
from a 12gb gaming card to 2x dgx spark, here's the model i'd run at each tier, the speed i measured and the settings that make it work, bookmark this:
> 12gb: bonsai 2 27b ptq1_0 with the mtp head, 50 tok/s fresh on a 3060. kv cache at q4_0, one slot, n-max 1 on the head and reasoning effort medium, because the default xhigh can think through your whole token budget and hand you an empty answer.
> 24gb: qwen 3.8 27b q4_k_m, 41.1 tok/s on a 3090 with mtp off and 65.8 tok/s with it on, at a 131k window. add --spec-type draft-mtp --spec-draft-n-max 2 --parallel 1 to llama-server and keep kv at q4_0, f16 kv hits a wall between 90k and 131k on 24gb.
> 1x dgx spark: moes, since it has 273 gb/s of bandwidth. qwen 3.8 flash next ud-iq4_xs does 44.4 tok/s in llama.cpp and ling 3.0 flash on the official int4 does 38.7 tok/s in vllm, both with mtp on.
> 2x dgx spark over connectx: qwen 3.8 flash next official fp8, tensor parallel across both boxes, 45 tok/s fresh and 35 tok/s mid-build with mtp, full 262k context with vision.
the rule under every tier is the same, decode tops out at your memory bandwidth divided by the bytes read per token, which is why a 1.75 bit file flies on a 3060 and why a 180b moe that only reads its active experts per token flies on a spark.
here's the order i'd go into local ai, anon:
> 12gb: learn the stack on a compressed 27b, how a model gets served, how an agent runs overnight with features like hermes agent's /goal. you will see good results and see some light at 50 tok/s fresh.
> 24gb: this is where you meet the king, none other than the one and only 27b dense q4. get 2x 3060 if you want hands-on tensor parallel, or one 24gb card if you want to scale correctly and efficiently. at 24gb i prototype about 30% of my daily work, that's where owning your thinking starts.
> skip macs and the 5090 and the rtx 6000 pro for now, learn the stack small first and understand the difference. it's not a thing that happens overnight, it's a process and a lifestyle, you don't just start doing everything, get disappointed and then never realize how profound this is, that you can think and it stays on your metal.
> dgx spark: go gentle, and if you don't want to learn pcie lanes, power distribution and bifurcation, the dgx spark path is a clean cuda box, plug in and go. you can stack more and with the connectx cable it spits well. i have 2 dgx sparks so i can say for sure scaling with dgx spark is the cleanest. sure you don't get super fast bandwidth for dense models, but moes like qwen 3.8 flash next, ling flash and stepfun 3.7 dance on a single dgx spark and go zoom.
> but if you want to learn real infrastructure, from cable management to pcie lanes at x8 and x16, bifurcation, slimsas cables, backplanes, airflow and power distribution, that's what the dgx spark skips for you, and the price is bandwidth. the ultimate path is the rtx 6000 pro path if you dare touch fire, and the fire doesn't care about dense or moe, it just burns everything, which i only intend to.
rejoice my fren
If you want to run a model at the best performance prompt with this
- say "use remote latest sglang/vllm"
- say "no enforce eager, no disabling cuda graphs"
- say "always enabled MTP/Vision/Reasoning"
- say "do not set max tokens less than 128k"
- say "setup live observability"
MartSec retweeted
Avui és Santa Tecla i per tant és oportú recordar que el 17 de maig de 1321 va arribar a Tarragona el seu braç incorrupte. El rei Jaume II va enviar una expedició al Regne d’Armènia per adquirir-lo a canvi d’un tron d'or, 200 cavalls i 400 formatges mallorquins.
HUGE SPEED UPGRADE! for bonsai 2 27b dense on every rtx 3060, 3070, 3080, 3090, 4060, 4070, 4080 and 4090.
LIVE NOW on huggingface: ternary bonsai 2 27b ptq1_0 + the qwen 3.8 mtp head, the 5.9 GB file that fits 8gb and 12gb cards, on a single rtx 3060:
> 50 tok/s with the kernel, head on, code 53 tok/s
> 40 tok/s with the kernel, head off
> 27 tok/s stock with the head (the +8% everyone hit)
> 25 tok/s stock
and the output is bit identical with the head on, greedy, three prompts, byte for byte, flag on vs off. the other grafts flip near ties, this one doesn't, the kernel is batch invariant.
three mtp grafts existed before this one, all on the 7.2 GB pq2_0 file, credited on the card. this one is the official ptq1_0 weights untouched, 851 tensors byte for byte, with the kernel that makes the head pay. fat file runs on the stock prismml binary today, no patch, the speed needs the kernel branch, and there is a prebuilt linux tarball next to the gguf, driver only, go download and you run.
the tarball covers every rtx 30 and 40 series card, 3050 to 3090 and 4060 to 4090. 12gb and up get the head and the 50 tok/s, 8gb cards get the kernel on the plain file at a 96k window, rtx 50 series builds from the branch in one cmake line, the blackwell fix landed tonight.
huggingface.co/sudoingx/Tern…
your rtx 3060 was running bonsai 2 at 26 tok/s this morning and now does 40 tok/s, i spent the day inside the prismml llama.cpp fork so your rtx 3060 can rejoice.
the kernel that reads the weights was leaving two thirds of the card's threads idle on the biggest matrices. i fixed it, tested it against the cpu reference, the outputs are bit for bit the same, and both PRs are open on their repo.
then i grafted the qwen 3.8 mtp head back onto the file, the one they dropped in the export, and with a batch invariance switch speculative decoding is lossless: 50 tok/s, twice what the stock fork does, and the words do not change.
every number on this chart is one rtx 3060 gpu, one night, llama-bench and a streaming client, the depth curve is the honest part, past 64k the attention layers reading the cache set the pace, so the gain narrows from 1.5x to 1.16x.
anyone can run it tonight, the branch, the graft tools and the serve lines are in the replies. if you own a 12gb card you were never behind, the kernel was.
the repo is below for anyone who wants to run it.
the timeline spent two days saying bonsai 2 cannot build. here is 1 hour 24 minutes of it building, one shot, from one paragraph, on an rtx 3060 12gb, sped to 8x so you can watch the whole thing.
what you are watching is a 5.9gb ternary compression of qwen 3.8 27b, served through the prismml llama.cpp fork with the full 262k window resident, writing a terminal gpu monitor in one html file. it thinks, it calls a tool mid build, it keeps going until finish. the clock in the corner is real. 8x, one frozen recorder stretch cut, nothing else touched.
for anyone new here, the 3060 is the most owned gpu on steam, a five year old card, and this is the kind of card the model was compressed for. for anyone who followed july, bonsai 1 built the wankel engine on an 8gb 3060 ti, this is the sequel one tier up.
the numbers, live server, thinking on
> 26 tok/s fresh, 22 at 12k, 18 at 35k, 13 tok/s at 77k deep
> 262k context resident on 11.7 of 12 gb
> 76k tokens, 77 minutes, 149 of 150 w the entire run
if you own a 12gb card, this runs on it tonight. serve line, model, fork and the exact prompt in the replies.
Blessings!
Google offers 16gb v100s for free 30 hours a week through Google colab
If you want to try self hosting but lack the compute, well here’s your chance
1. Learn to host
2. Learn to write the model into your infra
research.google.com/colabora…
Qwen3.8-27B now runs on 8GB of VRAM!
That's less than 500$ to run a model smarter and more capable than:
1. GPT-5.6-Luna High
2. Opus-4.6-Max
3. Gemini-3.1-Pro
And ties with:
1. GLM-5.2 Max
2. Gemini-3.6-Flash
PrismML has the mandate
Readers added context they thought people might want to know
The cited rankings reference Artificial Analysis benchmarks for full-precision Qwen3.8 27B (score 34), not PrismML's quantized ternary version which retains 98.2% of the base per its own benchmarks with no independent eval on this index.
artificialanalysis.ai/models/qwen3-8…
prismml.com/news/bonsai-2-…
MartSec retweeted
Bonsai 27B is breaking local AI again!
I'm soo excited to try this on my M1 Air 16GB.
Getting 98.2% of qwen3.8-27b fp16 on ternary build is just insane no matter how you think about it.
You'll need to give it a try.
Run Bonsai 27B locally on a 16 GB Mac 🥷
Bonsai 2 27B is @PrismML's ternary build of Qwen3.8 27B that keeps 98.2% of FP16 quality in 7 GB, it made a voxel Japanese pagoda in one prompt with Three.js!
Run AI models locally - atomic.chat
MartSec retweeted
🧵Apunts sobre tecnologia i repressió:
L'11S deixa 21 detinguts en dos dies, 10 d'ells menors. Òmnium i Alerta Solidària parlen de detencions arbitràries a l'Arc de Triomf.
Però la part de la repressió que no surt a les fotos comença l'endemà, quan les càmeres ja s'han apagat.
MartSec retweeted
When OpenAI was founded in 2015, sold as the "ethical" alternative to Google, I wrote a letter because I was so infuriated by the media framing them as an "altruistic" company.
Then I saw the same movie on repeat with Anthropic.
Now the same movie with the "whistleblowers"🙄
Anthropic Is building a surveillance system to monitor activists using a “pre-crime” approach that tries to predict incidents before they happen.
The extensive monitoring system that the AI company is building is aimed primarily at keeping tabs on activists who oppose the rapid development of artificial intelligence.
More from @DRBoguslaw below:
prospect.org/2026/09/09/anth…



























