Hi - Head of engineering for Cloudflare’s developer products here.
We do have an ongoing issue that is causing some customers to experience elevated long tail latencies. These are generally occurring above p999 and are usually on the order of single digit seconds. Queries taking 20+ seconds would be outside the norm and unexpected especially if this is happening more frequently.
Our team is working quickly to resolve it and we are expecting improvements to be released Monday. If you are seeing latencies that are substantially worse than this please drop me an email with your account and database identifiers byule at cloudflare
I wanted this when D1 was first teased, and before I figured out that D1 is a database product that happens to be built on SQLite rather than SQLite being the star of the D1 show. Nonetheless, what I want is to be able to point a CF tunnel at a local SQLite file and instantly be able to leverage all the benefits of D1.
I should be able to...
1. Configure a CF tunnel through the config file or the dash, pointing it to a local path of an existing SQLite file.
1a. On startup, the SQLite file should create and link a new D1 db.
2. Configure a CF tunnel through the config file or the dash, pointing it to an existing D1 db.
2a. On startup, the local sqlite db should be either overwritten or created.
3. Create read replicates through CF tunnels on another server or the local computer/wrangler for development.
4. Have automatic global read replicas on the edge, which is inherent to D1 no?
5. Have automatic/rolling backups and export and import those backups automatically with S3/R2.
6. Do a PITR through the dash or CF tunnel CLI.
6a. PITR should be possible to either the existing live DB or restoring it into a separate new D1 copy.
7. Leverage my SQlite files in workers, another automatic bonus of connecting it to D1.
There are likely plenty of more cool things that could be done if D1 could be exposed as a normal SQLite file. Ultimately, CF tunnels are just in the mix because it seems like the obvious choice for plumbing SQLite files into and out of the CF network/edge.
Boats small enough to be operated by a single person are required by law (I believe) to be fitted with a kill switch that is supposed to be clipped onto the operator. In the event they go overboard, the engine shuts off.
Of course in practice almost nobody actually uses these.
> Of course in practice almost nobody actually uses these.
The damn government can’t tell me what to do.
Sigh, I see plenty of people driving with the seatbelt behind them, which means they make the choice to ignore the advice. Imagine having to take action without being constantly told to.
Some deliberately do it out of principle, despite knowing it's dumb. I have a family member who refuses to wear his seat belt simply because the government shouldn't tell him what to do. He knows it's safer, and knows that he'll get a ticket if he's pulled over, but won't do it, purely out of this weird, dogmatic anti-authority.
In the field of aviation, they study aeronautical decision making (ADM), and hazardous attitudes that prevent good decision making. The FAA identified the so-called 5 Hazardous Attitudes[1], and number one on the list is "Anti-authority". I wouldn't be surprised if this attitude is causal of accidents and negligence in other activities like boating and driving.
Given how the country was essentially founded by "anti-authority" and still somewhat values freedom highly, it's not so surprising. IMHO it's not a bad thing as long as it's done in moderation.
>... plenty of people driving with the seatbelt behind them ...
There is a gadget which had some diffusion here (the manufacturer explicitly states that it is not tested/approved and actually prohibited for human use, but we all know how it is used in real life), tellingly called "Zitto" (would translate to "shut-up"):
B2 documentation suggests that after adding a CNAME (eg. cdn.ente.io) for their bucket endpoint (eg. bucket.s3.eu-central-003.backblazeb2.com), you will be able to replace the latter with the former. This breaks with the native B2 APIs with the following error:
We do have an ongoing issue that is causing some customers to experience elevated long tail latencies. These are generally occurring above p999 and are usually on the order of single digit seconds. Queries taking 20+ seconds would be outside the norm and unexpected especially if this is happening more frequently.
Our team is working quickly to resolve it and we are expecting improvements to be released Monday. If you are seeing latencies that are substantially worse than this please drop me an email with your account and database identifiers byule at cloudflare