cheers for correcting the gist, i've shared it with the team internally

MMax (@rozenmd)cheers for correcting the gist, i've shared it with the team internally

Varna•4/12/24, 12:48 PM

It's just that, there's a lot of content on D1, D1 in pages, docs of each and blog. Your velocity is so great that I can't catch up :meow_party:

I added some more comments on topic

https://gist.github.com/varna/07334fac76e4479a2fc950051131a34c?permalink_comment_id=5021183#gistcomment-5021183

Varna•4/12/24, 12:51 PM

I know that D1 is actually pretty simple compared to some other options. But when I jump around all sorts of different projects and tasks... I would just love to have a simple foolproof promt, that would explain what is the current state, and what can I do with it.

HHello, I’m Allie!Could you pass in an RPC target that makes reads only to their “namespace”?

Beny•4/12/24, 2:07 PM

Yeah that could definitely work!
I wonder if the arg to pass bindings down to the user worker are working yet (last I heard about it was a year ago)

mau•4/12/24, 4:13 PM

Migration workflow with orm is work(messy). Because you generate the sql file and apply it using the command line. Am I missing something?

mau•4/12/24, 4:13 PM

I am using drizzle orm

Mmau Migration workflow with orm is work(messy). Because you generate the sql file an...

Varna•4/12/24, 4:29 PM

If I remember correctly:

use drizzle-kit to generate .SQL
run wrangler d1 migrations list --localwrangler d1 migrations list --local or --remote--remote to check if it's up
2b. if it's not, you might want to change migrations folder in wrangler.toml or drizzle config
run wrangler d1 migrations applywrangler d1 migrations apply

mau•4/12/24, 4:31 PM

Thanks for detailed steps, I will give it a try!

Mmau Thanks for detailed steps, I will give it a try!

Varna•4/12/24, 4:32 PM

// Path: drizzle.config.ts
import { defineConfig } from "drizzle-kit"

export default defineConfig({
  schema: "./drizzle/schema.ts",
  out: "./migrations",
  driver: "d1",
  verbose: true,
  strict: true
})

// Path: drizzle.config.ts
import { defineConfig } from "drizzle-kit"

export default defineConfig({
  schema: "./drizzle/schema.ts",
  out: "./migrations",
  driver: "d1",
  verbose: true,
  strict: true
})

my drizzle config

Varna•4/12/24, 4:33 PM

and drizzle-kit generate:sqlitedrizzle-kit generate:sqlite script command for drizzle, instead of wrangler d1 migrations createwrangler d1 migrations create

mau•4/12/24, 5:06 PM

This is much better!!!! Thank you

mau•4/12/24, 5:06 PM

Also, studio is available??

mau•4/12/24, 5:06 PM

I can’t find any documentation for that too

Hannes•4/12/24, 8:39 PM

Hi, I'm about to port my port my application to Cloudflare Workers, but when testing, I noticed that my page load times increased quite a lot in comparison to the current deployment using node on a VPS. I traced it down to D1 having quite a bit of ~~query~~ latency - statement.runstatement.run takes about 30 - 32ms for very simple queries (like adding or deleting a row to a table with 5 columns). Is that expected?
In this blog post https://blog.cloudflare.com/d1-turning-it-up-to-11#turning-it-up-to-11 I read something about 1.8ms which would be much better

Thanks in advance!

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.

Hannes•4/12/24, 8:40 PM

Makes sense - but would you expect 30ms round trip?

Hannes•4/12/24, 8:42 PM

The 30ms is not from my local pc at home, but from the cloudflare worker to D1...

Hannes•4/12/24, 8:44 PM

I've set the location hint to EU, that's where I am, too. I just find it hard to believe that 30ms, because if your app is doing 10 round trips requests to the db, that would already sum up to 300ms...

HHannes I've set the location hint to EU, that's where I am, too. I just find it hard to...

Chaika•4/12/24, 8:46 PM

EU west or EU East?

CChaika EU west or EU East?

Hannes•4/12/24, 8:47 PM

EU West

Chaika•4/12/24, 8:47 PM

https://where.durableobjects.live/region/weur so it could be in any one of those

Where Durable Objects Live

Western Europe(region) | Where Durable Objects Live

Tracking where Durable Objects are created, wherever you are in the world.

Chaika•4/12/24, 8:48 PM

If you go to /cdn-cgi/trace/cdn-cgi/trace, ex: https://yourwebsite.com/cdn-cgi/tracehttps://yourwebsite.com/cdn-cgi/trace, colo= the airport code of the location you hit

Chaika•4/12/24, 8:49 PM

although I suppose that wouldn't be too helpful because we still have no clue where your DB ended up lol

Chaika•4/12/24, 8:49 PM

You could be in Germany and the DB could be in Spain

Chaika•4/12/24, 8:51 PM

eitherway there's going to be some network latency. You could enable Smart Placement on your worker bound to the database so that it tries to get placed "close" but the 1.92ms mentioned in the blog is purely just sqlite query procesing time

Hannes•4/12/24, 8:55 PM

OK, thanks for the info!

Max (@rozenmd)OP•4/12/24, 8:59 PM

our perf isn't worth measuring before read replicas go live tbh

MMax (@rozenmd)our perf isn't worth measuring before read replicas go live tbh

Chaika•4/12/24, 9:00 PM

kind of a funny thing to say about a GA product

Chaika•4/12/24, 9:00 PM

still writes will have to go back to the main one anyway

Chaika•4/12/24, 9:00 PM

and Smart Placement can help a great deal if you need to make more then one query

CChaika kind of a funny thing to say about a GA product

Max (@rozenmd)OP•4/12/24, 10:08 PM

is it though? depends what GA means to you, i guess

Original message was deleted

Chaika•4/12/24, 10:28 PM

Even replication/performance aside, if we compare it to other offerings and typical use cases, the low storage limit becomes an issue. We're told D1 is different and wants a different approach (not unlike Turso), but then we're not given the tools to use that different approach on GA.

Chaika•4/12/24, 10:29 PM

Kind of like ordering a cake, getting one of the slices and being told it's ready, and the rest will come later.. that's what beta is for, not GA

Chaika•4/12/24, 10:30 PM

it's just kinda meh, I can forsee a lot of issues people using this "GA" product and being forced to use beta/alpha read-replicas or dynamic bindings to use it for a very typical use case, misaligned expectations

kian•4/13/24, 9:49 AM

there’s a d1 export command in Wrangler

Jjbithell I'm not sure if I'm missing something - but how do we run these migrations autom...

bun•4/13/24, 1:06 PM

what does it mean migrations are not run in production ?

bun•4/13/24, 1:06 PM

you can migrate your prod db by providing --remote--remote flag

James•4/13/24, 2:10 PM

This is why marketing is so important to be explicit. Some people still believe to this day that D1 is (actually) globally distributed:

https://www.reddit.com/r/CloudFlare/comments/1c2a7im/is_d1_rest_api_performant_and_production_ready/kz8u3i5/

cortadomaltese's comment on "Is D1 rest api performant and producti...

Explore this conversation and more from the CloudFlare community

James•4/13/24, 2:15 PM

sadly, yes, same misleading marketing problem

João Castro•4/13/24, 2:17 PM

Then what does "Globally distributed" means here?

James•4/13/24, 2:19 PM

Yeah. It's globally distrubuted in the sense that I can create a DB in EU, US, etc. but individual DBs are not "distributed", or "replicated"

João Castro•4/13/24, 2:20 PM

lol

James•4/13/24, 2:20 PM

Read replication is coming, and was talked about briefly in https://blog.cloudflare.com/making-full-stack-easier-d1-ga-hyperdrive-queues, but it's not here yet

João Castro•4/13/24, 2:20 PM

In the case of D1 i understand its upcoming

João Castro•4/13/24, 2:20 PM

But for R2 thats a bad look

João Castro•4/13/24, 2:21 PM

Not the kind of thing i usually expect from Cloudflare, to be honest

oof2win2•4/13/24, 4:01 PM

whats the eta on d1 read replicas?

CChaika and Smart Placement can help a great deal if you need to make more then one quer...

Hannes•4/13/24, 5:43 PM

Yes, definitely. I enabled that and it solved my issue completely. Now the whole page load time is faster than on my VPS with a local mysql db.

Iippa just putting my 2 cents into the above discussion about d1. I actually thought i...

Beny•4/13/24, 6:48 PM

The concept is that you should be giving each of your users (or system components) their own database for only their data, rather than having one huge database everyone's combined data is stored in. It's about changing the way you think about the data storage in your application.
Understandably the 10GB limit sounds small, but in reality it is a lot of space for a database. You can fit millions of records into it while remaining under the limit. My biggest db for example has 15 million records across 200 tables, and is just over 2.5 GB.

cheers for correcting the gist, i've shared it with the team internally

Similar Threads