masklinn

9 ms·

91.
by masklinn 3mo ago
> Why uuid7, is the btree performance better with it than with uuid4? Yes, being ordered uuid7 leads to less splitting and index bloat than the fully random uuid4. So while the lookup is pretty similar the index is in much better shape.
92.
by masklinn 3mo ago
The article does not say it’s storing the authenticator data (in the format the webauthn spec specifies), it says it’s storing (most of) the fields in cbor. So it’s using the webauthn reference for logical purposes (the names and types of
93.
by masklinn 3mo ago
Obviously. You also need to profile to make sure this is actually a hit spot, deploying unsafe to remove bounds checks which account for ~0% of runtime is a waste of effort. And as the essay mentions there are also “hints” you can give the
94.
by masklinn 3mo ago
A big part of it is taxes, European countries tend to tax fuel pretty heavily. If heating oil is still a thing where you are, compare its prices to diesel (especially historically). They’re nearly the same product, the difference is almost
95.
by masklinn 3mo ago
On the continent, afaik most countries work on a lease system, you rent a plot for a few decades (which may or may not be renewable). Some countries have a “perpetual” lease with an ongoing fee, a few years after the payment stops the plot
96.
by masklinn 3mo ago
> and presumably other things? Various statistical views over the value distributions of the indexes, so that the planner can estimate how useful (selective) the index should be. sqlite_stat1 just gives an average (number of records in t
97.
by masklinn 3mo ago
> omg you're right. Another example of SQLite's type-flimsyness. You're just firing on all the bullshit cylinders in your little motorised gish gallop aren't you? The only RDBMS in widespread use which supports unsign
98.
by masklinn 3mo ago
> SQLite will gladly store a u64::MAX as a "unix timestamp" SQLite does not support unsigned integers. > Try reading that back in any application date/time code and your app probably crashes immediately. Postgres will h
99.
by masklinn 3mo ago
It’s perfectly fine if your write throughput is low, especially in wal mode. Multiprocess does not actually change much if anything, even in multithreaded mode you want every thread to have its own connection and to have a good handle on wh
100.
by masklinn 3mo ago
In fairness, sqlite is perfectly happy with Julian dates or Unix timestamps (that’s the affinity of a column typed “datetime” in non-strict mode) and timestamp(tz) are nothing to write home about except in complaint.
101.
by masklinn 3mo ago
Yup, every alternative rebar has drawbacks which causes increased costs or different failure modes which is why they tend to be used in specialised applications where they are necessary .
102.
by masklinn 3mo ago
> Stainless steel rebar could be used There are also coated and non-metallic rebars.
103.
by masklinn 3mo ago
The 360 was a multithreaded machine, it had 3 physical cores with hyperthreading (so 6 logical cores). The PS3 was a completely different beast, it had a single general purpose core (hyperthreaded) with 6 user-accessible vector coprocessors
104.
by masklinn 3mo ago
The 360 had 3 cores. The PS3 had a single core with vector coprocessors on a ring bus. GPGPU is what displaced the Cell SPEs, and you wouldn’t count that as cores. In fact the PS3 originally didn’t include a GPU, the SPEs were supposed to h
105.
by masklinn 3mo ago
> upb parses FAST, but then every access is still C->Python and it slows it down. So for many reads the slow python one can win? That is pretty unlikely. TFA's version is in Rust and just barely edges out upb.
106.
by masklinn 3mo ago
> I don’t know what black magic Google uses for the Python implementation, but the classes it generates are totally opaque and impossible to inspect. TFA seems to say that they’re just thin proxies over the underlying C++ APIs, which wou
107.
by masklinn 3mo ago
You do not. SQLite date/time functions work with time-values which can be ISO timestamp strings, Julian fractional day numbers, or Unix timestamps. See https://sqlite.org/lang_datefunc.html for the details.
108.
by masklinn 3mo ago
A comment will do more than a nonsensical type which is not enforced: it won’t have the wrong affinity, it will spell out what the concrete type is, and there’s no limit to what it can specify. Domain types would be the best fix, but I do n
109.
by masklinn 3mo ago
The serious limitation is that you create a column as date, you don’t understand what sqlite does with it, and you start storing strings in there, at which point everything is confused. You can use comments to preserve intent in strict mode
110.
by masklinn 3mo ago
> Midgley is complicit, but he's just a small piece. Midgley used to tour around “proving” the safety of leaded gas by pouring it on his hands. And had to be treated twice for lead poisoning. He was very much a culprit.
111.
by masklinn 3mo ago
The intent of ANY is obviously that the values be flexible. That’s why it’s there if you need it.
112.
by masklinn 3mo ago
numeric is not a type it’s an affinity, the underlying types are real and integer. That is why numeric is not valid on strict tables.
113.
by masklinn 3mo ago
You can be flexible with strict tables, type every column as ANY and you pretty much get back the original behaviour.
114.
by masklinn 3mo ago
> some data types are not available, such as Date. That’s not a type, you just get a numeric-affinity column.
115.
by masklinn 3mo ago
> Instead, you're expected to just use a text column and store a textual timestamp. You can actually use an integer column and store Unix timestamps (or floats for subsecond accuracy). But yes, sqlite has very little types support
116.
by masklinn 3mo ago
> Claims do not support themselves. The claim is unsupported by evidence and thus the burden of proof is on them or you to produce that evidence. OK? > Your argument that the poster needs to go read, implement, integrate, and benchmar
117.
by masklinn 3mo ago
> I can evaluate the claim now And the article is now. What luck! > I would not have been able to evaluate the speed gain of an Oracle database using whatever proprietary implementation they are using. Which has nothing to do with the
118.
by masklinn 3mo ago
TFA is a post by the author of the algorithm, talking about the performance they originally predicted and later observed after implementing it while they were working at oracle, now that the patent has expired and anyone can implement the a
119.
by masklinn 3mo ago
Even if you “rely on countless unsafe blocks”, unsafe is additive, it gives access to additional APIs which are not checked. It does not disable affine types, the borrow checker, or send/sync traits. Unless the entire codebase is unsaf
120.
by masklinn 3mo ago
> In Python, this works correctly for negative values. They’re both “broken” in different ways. Arguably C’s brokenness is more apparent and less useful but Python also has footguns: C uses truncated division for its “modulo” so the rema

More ›