@elithrar @rozenmd I wrote a code for D1. However, this code gives the following error when there ar

@elithrar @rozenmd I wrote a code for D1. However, this code gives the following error when there are too many requests:

{
    "message": "Error while checking rows: Error: D1_ERROR\n    at D1Database._send (worker.js:149:13)\n    at async D1PreparedStatement.all (worker.js:215:7)\n    at async Object.fetch (worker.js:11:18)"
}

{
    "message": "Error while checking rows: Error: D1_ERROR\n    at D1Database._send (worker.js:149:13)\n    at async D1PreparedStatement.all (worker.js:215:7)\n    at async Object.fetch (worker.js:11:18)"
}

{
    "message": "Error while checking rows: Error: D1_ERROR\n    at D1Database._send (worker.js:149:13)\n    at async D1PreparedStatement.all (worker.js:215:7)\n    at async Object.fetch (worker.js:11:18)"
}

{
    "message": "Error while checking rows: Error: D1_ERROR\n    at D1Database._send (worker.js:149:13)\n    at async D1PreparedStatement.all (worker.js:215:7)\n    at async Object.fetch (worker.js:11:18)"
}

Can I send the code via pm?
NOT:*It works with few users. but it does not work when there are many instant requests.

Llokiwind @elithrar @rozenmd I wrote a code for D1. However, this code gives the following...

Matt Silverlock•5/31/23, 3:00 PM

Better to post it here: we can't formally/directly support folks via DM, but others may be able to help

Ccam "D1 storage operation exceeded timeout which caused object to be reset"

Matt Silverlock•5/31/23, 3:05 PM

What's your database ID? And is this on the --experimental-backend--experimental-backend or the original alpha backend?

Ccam its on the experimental backend, ff81e8fa-1199-43d0-ac0b-1c8c14e8ef12

Matt Silverlock•5/31/23, 3:12 PM

Perfect, thanks. Let me see if I can track down the log entry on our side.

Eemppu When D1 is released with read replication, will D1 charge for only a single writ...

Max (@rozenmd)•5/31/23, 7:00 PM

Importantly, when we enable global read replication, you won’t have to pay extra for it, nor will replication multiply your storage consumption

Max (@rozenmd)•5/31/23, 7:00 PM

https://blog.cloudflare.com/d1-turning-it-up-to-11/

The Cloudflare Blog

D1: We turned it up to 11

We've been heads down iterating on D1, and we've just shipped a major new version that's substantially faster, more reliable, and introduces Time Travel: the ability to restore a D1 database to any point in time.

MMax (@rozenmd)> Importantly, when we enable global read replication, you won’t have to pay ext...

itsmatteomanf•5/31/23, 8:23 PM

One question I have about read replication, would it improve performance when writing to the DB? I now see a reduction in performance on write when running any sort of SELECTSELECT query, will those be split to a separate replica?

itsmatteomanf•5/31/23, 8:23 PM

And secondary question, any ETA on backups on the experimental backend? It's very hard to export data now, even a manual backup would be great in the meantime.

Iitsmatteomanf One question I have about read replication, would it improve performance when wr...

Matt Silverlock•5/31/23, 8:35 PM

Clients will read from the (geographically) nearest read replica. That may sometimes be the leader (write+read). What kind of perf reduction are you seeing here?

Matt Silverlock•5/31/23, 8:36 PM

(Per the blog) We're entirely moving to Point in Time Recovery for the foreseeable future vs. snapshot based backups, since PITR is a) infinitely more flexible and b) is better than snapshots in terms of actually restoring your DB. What you won't be able to do until GA is export a DB directly.

MMatt Silverlock Clients will read from the (geographically) nearest read replica. That may somet...

itsmatteomanf•5/31/23, 8:45 PM

Not much, tbh, but I've doing a lot of requests and I saw some slowdowns after a couple of queries in the console (somewhat big, but not massive ones). Understood. Will check next time the queue runs and in case report back

One thing I'm not sure about is ~~where would a scheduled Worker run and, more importantly~~ (this was dumb lul

) where the consumers for queues would run to locate the db closer to there (especially with the replicas on the horizon as the users would hit only the read side)

MMatt Silverlock (Per the blog) We're entirely moving to Point in Time Recovery for the foreseeab...

itsmatteomanf•5/31/23, 8:45 PM

I see, so the wait is for the Time Travel feature... hopefully soon!

itsmatteomanf•5/31/23, 8:46 PM

A good export option would be nice regardless, tbh

Iitsmatteomanf A good export option would be nice regardless, tbh 🙂

Matt Silverlock•5/31/23, 9:06 PM

We'd need to solve import - you may not care, but many others will. Import is also tricky to solve.

Iitsmatteomanf Not much, tbh, but I've doing a lot of requests and I saw some slowdowns after a...

Matt Silverlock•5/31/23, 9:06 PM

You shouldn't typically see a slowdown as our storage implementation is non-blocking (it's effectively a WAL-mode implementation):

WAL provides more concurrency as readers do not block writers and a writer does not block readers. Reading and writing can proceed concurrently.

MMatt Silverlock We'd need to solve import - _you_ may not care, but many others will. Import is ...

itsmatteomanf•5/31/23, 9:07 PM

Oh yeah, I had to bypass that, too... but you can use a very big .sql.sql file if you really want to (up to a point)

MMatt Silverlock You shouldn't typically see a slowdown as our storage implementation is non-bloc...

itsmatteomanf•5/31/23, 9:08 PM

It might have been something else, unfortunately I don't have just DB calls, but also a 1.1.1.11.1.1.1 fetch and it's a queue consumer, so who knows. Will report back if it becomes a pattern

Zzszszsz What is the recommended way to get the row_id (or sth) from a `insert or ignore`...

Max (@rozenmd)•6/1/23, 8:19 AM

RETURNING *RETURNING *

Zzszszsz Hmmm...how ?

Max (@rozenmd)•6/1/23, 8:20 AM

INSERT INTO some_table (name) VALUES ('something') RETURNING idINSERT INTO some_table (name) VALUES ('something') RETURNING id for example

Max (@rozenmd)•6/1/23, 8:21 AM

saves you a round trip to the db

Leon338•6/1/23, 6:18 PM

Hello, Quick Question about the Pricing. So for example I have a ordered List of IDs and select one small single Entry, it would maybe count as 4-5 Reads and now if I compare it to KV it would be 100x cheaper to retrieve a single Entry. And once there is Read Replication it'll be fast, too. My Question is how can it be so much cheaper? Like I understand the Pricing has to be like that for bigger Queries, but sounds to good to be true

Leon338•6/1/23, 6:20 PM

I know. Have you read the Question?

Leon338•6/1/23, 6:21 PM

No the Database Solution would be 100x cheaper. Even tho it would count some reads on writing for the Index

@elithrar @rozenmd I wrote a code for D1. However, this code gives the following error when there ar

Similar Threads

Similar Threads

Similar Threads