I personally wouldn't use D1 as a primary due to the nature of D1 being so far from potential worker

I personally wouldn't use D1 as a primary due to the nature of D1 being so far from potential workers depending on your user base, the latency isn't good. During my own testing the extra 100-500ms latency per worker request due to multiple round trips to D1 wasn't worth it.

It forced me to use the DO SQL engine instead and refactor my app to per-user DBs which I feel is a more scalable design.

JJames I personally wouldn't use D1 as a primary due to the nature of D1 being so far f...

elpupper•11/21/24, 5:37 PM

how/why are you doing multiple round trips to D1?

MMax (@rozenmd)Is this a free account, or do you pay for Workers btw?

deternal•11/21/24, 6:13 PM

We use workers paid account, we have about 15 D1 databases and each one is less than 5 gb, so I doubt it crossed the 250 gb account wide threshold. The "Exceeded maximum DB size" errors show up for some time and then resolve on it's own, which is what it makes harder to understand if the db size actually breached 10gb or not, the UI's d1 db size is what we are use to decide to change the db, but these errors show up even when the db size is less than 2gb in the UI. Any tips would be gratly appreciated.

Eelpupper how/why are you doing multiple round trips to D1?

JamesOP•11/21/24, 6:22 PM

web app makes all kinds of D1 requests on a worker request, get session, get user, update user etc. Each SQL stmt is a round trip.

JJames web app makes all kinds of D1 requests on a worker request, get session, get use...

elpupper•11/21/24, 6:56 PM

100 ms seams reasonable. but 500 doesnt. You should consider not splitting up your statements and write real SQL language. I'm not making fun of you FYI a lot of people including me have a issue of splitting up queries when realistically it can be one query.

Eelpupper 100 ms seams reasonable. but 500 doesnt. You should consider not splitting up yo...

JamesOP•11/21/24, 7:05 PM

Already use straight SQL, there's no getting around some big requests with lots of disparate SQL for different purposes on a modern app. The downfall of D1 is that it's not colocated with the web server like many other services. Whats close for one user is far for another. Personally a db request should have sub 10ms latency from the web worker for simple queries. Closer to 1-5ms even or less.

elpupper•11/21/24, 7:06 PM

completely agree. The latency is a network latency tho thats the issue

elpupper•11/21/24, 7:06 PM

I had the same argument last time about it in this chat

MMax (@rozenmd)no - the bookmarks time travel uses are like pointers rather than actual copies ...

Isaac McFadyen•11/21/24, 8:36 PM

wonder if you could run a SQLite DB in WASM and then stream the client the WAL somehow: https://sqlite.org/wasm/doc/trunk/npm.md

elpupper•11/21/24, 8:36 PM

there is a sqlite client in WASM

elpupper•11/21/24, 8:36 PM

sql.js i believe

Eelpupper there is a sqlite client in WASM

Isaac McFadyen•11/21/24, 8:37 PM

The link I sent above is one yeah

Isaac McFadyen•11/21/24, 8:37 PM

Not really a client it's actual full SQLite

Isaac McFadyen•11/21/24, 8:37 PM

Oh yeah sql.js is also one

elpupper•11/21/24, 8:38 PM

https://github.com/sql-js/sql.js

elpupper•11/21/24, 8:38 PM

am i missing something about wasm?

elpupper•11/21/24, 8:38 PM

why wasm in the backend?

IIsaac McFadyen Not really a client it's actual full SQLite

elpupper•11/21/24, 8:40 PM

same with the one i sent i believe

Eelpupper why wasm in the backend?

Isaac McFadyen•11/21/24, 8:51 PM

If you are building a native application in JavaScript (using Electron for instance), or are working in node.js, you will likely prefer to use a native binding of SQLite to JavaScript.

They recommend against that actually

IIsaac McFadyen > If you are building a native application in JavaScript (using Electron for ins...

elpupper•11/21/24, 9:00 PM

Talking about cloudflare in general :NotLikeThis:

Eelpupper Talking about cloudflare in general :NotLikeThis:

Isaac McFadyen•11/21/24, 9:02 PM

Mainly because WASM is portable and secure. If you allowed anyone to upload binaries (as does AWS Lambda/GCP Cloud Run) then to get enough security you basically need to run them in a full, dedicated VM or at least gVisor (GCP). With WASM even though it's untrusted code, running inside the V8 WASM sandbox is secure enough.

Isaac McFadyen•11/21/24, 9:03 PM

And because it's running in V8 it's far lighter-weight than a VM/gVisor and they can afford to run thousands/tens of thousands of WASM sandboxes.

Isaac McFadyen•11/21/24, 9:05 PM

There's a good writeup here: https://developers.cloudflare.com/workers/reference/security-model/

Max (@rozenmd)•11/21/24, 9:27 PM

D1s alpha was SQLite in WASM on DOs, it was uh "fun" to operate

MMax (@rozenmd)D1s alpha was SQLite in WASM on DOs, it was uh "fun" to operate

elpupper•11/21/24, 10:42 PM

:kekw:

IIsaac McFadyen And because it's running in V8 it's far lighter-weight than a VM/gVisor and they...

elpupper•11/21/24, 10:42 PM

i will have to test this

elpupper•11/21/24, 10:43 PM

im working o nsomething similar to AWS lambda and CF workers using NixOS microvm.nix and firecracker

JJames Already use straight SQL, there's no getting around some big requests with lots ...

Burrito•11/21/24, 11:58 PM

Worker smart placement should help with this though, as it should put your worker closer to D1 rather than closer to user if it sees that you are making multiple round trips to D1. Read replica is also on the roadmap, although there doesn't seem to be any ETA for that.

Burrito•11/22/24, 12:04 AM

I'm also considering if I should build on D1 or DO + SQLite storage, but the latter having to pay extra for DO requests, as well as losing out on D1 features, are putting me off.

BBurrito I'm also considering if I should build on D1 or DO + SQLite storage, but the lat...

JamesOP•11/22/24, 12:13 AM

Had the same concern, what clinched it for me is the 10gb limit on d1. Audit trails, request logging etc eats that up quick. Only d1 feature I miss is dumping the SQLite file. Going custom on the rest isn’t hard.

Burrito•11/22/24, 12:15 AM

10 GB limit? Ah, maximum database size.

JJames Had the same concern, what clinched it for me is the 10gb limit on d1. Audit tra...

elpupper•11/22/24, 12:32 AM

make new dbs i guess

elpupper•11/22/24, 12:33 AM

but i swear cloudflare already does those for you

JJames Had the same concern, what clinched it for me is the 10gb limit on d1. Audit tra...

Burrito•11/22/24, 12:45 AM

DO SQLite currently only has 1 GB limit though, and doc seems to indicate that it will be raised to 10 GB when GA, which matches what D1 offers.

BBurrito DO SQLite currently only has 1 GB limit though, and doc seems to indicate that i...

JamesOP•11/22/24, 1:25 AM

1gb per user is reasonable for a multi tenant app. Can scale that to terabytes if needed. Much harder to scale d1 to 1tb.

SteffTek•11/22/24, 8:41 AM

Well i truly think my worker smart placement is bugged, it wont analyze anything anymore, not even stating something in the dashboard. has the minimum traffic for smart placement increased in someway?

SSteffTek Well i truly think my worker smart placement is bugged, it wont analyze anything...

Walshy•11/22/24, 9:04 AM

could you send me your account id please?

WWalshy could you send me your account id please?

SteffTek•11/22/24, 9:05 AM

Sure! Account ID is f61e2912c0937987fbd186d3523dc847 and our Dev Worker is called "worker-customer-devinc" (screenshot above is from one of our tenants)

Walshy•11/22/24, 9:05 AM

Thanks let me take a look

Walshy•11/22/24, 9:14 AM

So, it looks like smart placement was re-enabled 30 mins ago and yeah, so far it doesn't have enough requests

WWalshy So, it looks like smart placement was re-enabled 30 mins ago and yeah, so far it...

SteffTek•11/22/24, 9:14 AM

yeah i did it (a few times in fact) to see if it reappears

SteffTek•11/22/24, 9:14 AM

the other worker hadn't hat it reenabled and doesnt have it either

Walshy•11/22/24, 9:15 AM

I can check that one too, what's it called?

SteffTek•11/22/24, 9:15 AM

worker-customer-***

SteffTek•11/22/24, 9:15 AM

last deployment there was a month ago

Walshy•11/22/24, 9:18 AM

It looks like that also has pretty minimal traffic. looks like it was placed on the 13th and then not on the 15th - let me see what changed

SteffTek•11/22/24, 9:19 AM

Thx! The problem is each of our tenants won't have much traffic. we are a cloudbased cash register provider, so we only have a limited amount of users per tenant

Walshy•11/22/24, 9:21 AM

Ok I see what changed.. figuring out why

Walshy•11/22/24, 9:25 AM

Ok yep, looks like an issue our side - gonna let the team know!
Thanks for reporting, we'll get it fixed!

WWalshy Ok yep, looks like an issue our side - gonna let the team know! Thanks for repor...

SteffTek•11/22/24, 9:25 AM

<3 Thank you!!!

Kimitri•11/22/24, 9:43 AM

can someone help me with this. I'm trying to connect vitest with D1 local generated by wrangler dev, but it's not working, I use Vitest-pool-workers to do it with this configuration:

import { defineWorkersConfig } from "@cloudflare/vitest-pool-workers/config";

export default defineWorkersConfig({
  
  test: {
    globals: true,
    poolOptions: {
      workers: {
        isolatedStorage: true,
        wrangler: { configPath: "./wrangler.toml" },
      },
    },
  },
});

import { defineWorkersConfig } from "@cloudflare/vitest-pool-workers/config";

export default defineWorkersConfig({
  
  test: {
    globals: true,
    poolOptions: {
      workers: {
        isolatedStorage: true,
        wrangler: { configPath: "./wrangler.toml" },
      },
    },
  },
});

and to ensure I tried to show in the logs like this

import { Hono } from 'hono'

export type Env = {
  DB: D1Database
}
const app = new Hono<{ Bindings: Env}>()

app.get('/', async (c) => {

  console.log(c.env.DB)

  return c.text("Hello world!")
})

export default app

import { Hono } from 'hono'

export type Env = {
  DB: D1Database
}
const app = new Hono<{ Bindings: Env}>()

app.get('/', async (c) => {

  console.log(c.env.DB)

  return c.text("Hello world!")
})

export default app

and it's show undefined, it just show some data when I run wrangler dev,

import { defineWorkersConfig } from "@cloudflare/vitest-pool-workers/config"; export default defineWorkersConfig({ test: { globals: true, poolOptions: { workers: { isolatedStorage: true, wrangler: { configPath: "./wrangler.toml" }, }, }, }, });

import { Hono } from 'hono' export type Env = { DB: D1Database } const app = new Hono<{ Bindings: Env}>() app.get('/', async (c) => { console.log(c.env.DB) return c.text("Hello world!") }) export default app

I personally wouldn't use D1 as a primary due to the nature of D1 being so far from potential worker

Similar Threads

Similar Threads

Similar Threads