Activity Feed

AI & ML interests

None defined yet.

Recent Activity

homanp 
posted an update 7 days ago
view post
Post
152
We're super excited to introduce security-one: our open-weight model for security decisions.

Designed to:

✅ Run 24/7
✅ Assess signals across apps, agents and infra
✅ Return structured probabilities to guide routing
✅ Route suspicious events to stronger models/humans

superagent-ai/security-one-27b
  • 1 reply
·
anakin87 
posted an update about 1 month ago
view post
Post
3498
I made a 1.1M ModernBERT encoder play Doom in real time on a CPU

Some time ago, VAGO Solutions released SauerkrautLM-Doom-MultiVec-1.3M, a tiny model trained to play Doom Defend the Center scenario from 31k human gameplay examples.

My first thought: cool! I love both Doom and Small Language Models.

Then another idea: I bet I can do better :-)

What I did?
- evaluated the original model and found it's better than reported
- changed a bit the architecture
- generated SFT data with a scripted oracle
- SFT + PPO refinement on consumer hardware

Got a smaller, faster and killer model
Can even fit a floppy with int8 quantization 💾

Watch it play/read the article: anakin87/tiny-doom-defender
BramVanroy 
posted an update 2 months ago
view post
Post
2808
**I benchmarked HF buckets against https access for Common Crawl.**

Took me a while to get round to do this but I benchmarked access to Common Crawl via https vs hf buckets. Both experiments were run at night in Europe. I do not think other hardware problems were impacting the speeds since CPU processing time of the non-download pipeline components were highly similar (within 2% identical) and below only the WarcReader speeds of datatrove are used.

Experiment: selected 5 disjoint samples of 64 files each (randomly from the latest crawl; 20,499 docs/file). Those five batches were then processed by 32 single-core tasks with 4GB/core (five batches to calculate CIs). Paired experiment between using https and hf bucket.

- https: 40.0 [39.3-40.6] (seconds per WARC file)
- hf bucket: 172.0 [122.7-221.2]

That is a difference of about 4x in streaming speed. You'll see that https is also more stable (smaller CI).

I also ran raw throughput tests to the endpoints to measure rate limiting (64MiB transfer at 8/32/128/256 concurrent readers) and rate limiting seems not an issue for either: at any of those parallel reader numbers, their respective speeds stay about the same.

Note that, given CC scale, this is still a small test. Rate limiting may become more obvious when processing a full crawl. I do not know whether the https endpoint vs HF bucket will shut you out earlier with which limits.