HN user

mhio

386 karma

my

Posts2
Comments232
View on HN

Toms Hardware usually includes a "Sustained Write Performance and Cache Recovery" test

The test measures the write cache speed and the time to the fall to the native NAND write speed. There are usually irregularities in the sustained write speeds as well.

https://www.tomshardware.com/reviews/wd-black-sn850x-ssd-rev...

The other test I've seen is based on writing and using up free space, SSD performance can drop off as the free space fills up and garbage collection efficiency goes down. I think this impacts random writes particularly

In the enterprise space, drives tend to keep more over provisioned NAND free to maintain more consistent performance. Very early on the SSD timeline, it was advisable to only allocate 80% of consumer drives if you were using them outside of desktops and expected the workload to fill them.

A playright-mcp server, or any bidi browser automation, should be equally capable of discovering/injecting and calling the same client JS exposed MCP-B site API?

It's like an OpenAPI definition but for JS/MCP? (outside of the extension to interact with that definition)

50% of that is spam that is blocked. At least 50% of the rest is spamish but not spam spam.

So don't feel too overwhelmed!

What are the advantages to pljs over plv8? I thought the context creation would have been the big one, but it doesn't appear so in the current benchmarks.

How did the project weigh the intermittent updates of bellard quickjs and the community fork quickjs-ng?

What's the motive "to gain trust and encourage users to use AI on WhatsApp"? Meta aren't a charity. You have to question their motives because their motive is to extract value out of their users who don't pay for a service, and I would say that whatsapp has proven to be a harder place to extract that value than their other ventures.

btw whatsapp implemented the signal protocol around 2016.

The headers are seen by the monster-in-the-middle CDN.

It's obfuscation at best. I'm not sure the encrypted traffic will look particularly php-ish for example. Compressed formats might look vaguely passable.

I can't see any stenography code or libraries in the repo.

The pins/struts are a 2 point system that double as the booster lift points in general operations. The booster mostly hangs in tension which the existing tank structure can support. I would guess they share some of the structure beefiness with the grid fins.

Legs require at least 4 points, probably more. Shock absorption hardware, ability to unfurl to an acceptable width. Require reinforcement (cross bracing) near the base of the tanks to handle the loads pushing inwards toward the center of the tanks.

Would the profiles and resulting binaries be highly CPU specific? I couldn't find any cross hardware notes in the original paper.

The example's I'm thinking of are CPU's with vastly different L1/L2/L3 cache profiles. Epyc vs Xeon. Maybe Zen 3 v Zen 5.

Just wondering if it looks great on a benchmark machine (and a hyperscaler with a common hardware fleet) but might not look as great when distributing common binaries to the world. Doing profiling/optimising after release seems dicey.

SQLToy 2 years ago

Why is that? There doesn't seem to be anything particularly esoteric in the implementation.

Interesting, that's a requirement for an out of band tailing tool.

Maybe a user defined function bound to an INSERT trigger. But I believe that functions are also connection specific which is fine for the tail tool, but what happens when the user defined function connection goes away.