ZIn one of the blog posts 
1Durable Objects would be the best way forward here
Athe math aint mathing
HThat might be because the system that powers account-level analytics may be a bit behind the actual values
Aif thats the case, then that would be like a year behind
HWeird
Athat 3gb db has been well past that size for a loooong time
Anot the end of the world, but a bit odd 
AIs it possible to use a backend framework like fastify in a wrangler/d1 project? And what about postgres to make queries?
KIām encountering D1 slow response, like 500ms+, but my table only have 10 rows, the database is under APAC region. Is that expected?
KRequest without D1 fetch, around 30ms. With D1 fetch around 600ms
WWhere is your worker invoked?
WAnd are you using smart placement?
KAlso under APAC
Kdefault placement
ILighter Prisma is in the works.
The Kysely gap you described is solvable today-ish with plugins, and possibly in the future with some new APIs (but without turning the library into yet another ORM.)
The Kysely gap you described is solvable today-ish with plugins, and possibly in the future with some new APIs (but without turning the library into yet another ORM.)
KAlso when I create D1, if I donāt specific region, it will create in North America, but itās obviously far away from APAC. Is this recommended?
FHello everyone, does D1 have a boolean value? If not, what are the best practices for implementing boolean values on D1?
F
FAh, got it.
AHey all 
I'm a massive Cloudflare advocate in my big organization, and we use it heavily. So far we haven't been using D1 as we have no need. But I've started using it on a side passion project of my own.
So far everything works how I would like it, except that the Response time for basically any query (even the most simple ones) are very high.
I have a worker which serves as my API layer, and it calls the D1 internally. Every request takes over 2-3 sec to respond.
What is your experience with D1 response times?
Also to mention, the DB is very small ~12kb in total.
I'm a massive Cloudflare advocate in my big organization, and we use it heavily. So far we haven't been using D1 as we have no need. But I've started using it on a side passion project of my own.
So far everything works how I would like it, except that the Response time for basically any query (even the most simple ones) are very high.
I have a worker which serves as my API layer, and it calls the D1 internally. Every request takes over 2-3 sec to respond.
What is your experience with D1 response times?
Also to mention, the DB is very small ~12kb in total.
JThat seems to align with what others are reporting, depending on network latency, types of queries, db location, etc. I would be wary of using D1 in production though until there's some more guidance around error rates and types of errors, since they do seem to happen more than would be reasonably expected: https://github.com/cloudflare/cloudflare-docs/issues/18485
AInteresting. I've just joined Disc here, and I'm reading through history, where I'm seeing people having the same problem I'm having.
@James do you have some recommendation on what works well as a simple DB together with Workers?
@James do you have some recommendation on what works well as a simple DB together with Workers?
JI'd go with Postgres via https://neon.tech/ if you want something more featured than SQLite - you can pair it with Hyperdrive for some impressive latency/query times, or https://turso.tech/ if you want SQLite which I've heard good things about
AOk great, I will try it out. I might go with SQLite first as I've already built most of the queries/seeds etc. And I really need the most basic of stuff.
I appreciate the recommendations.
I appreciate the recommendations.
Ganyone using raw sql? or everyone using an ORM like drizzle? just curious. 
II previously used raw SQL and I moved to Drizzle. I still try to use Drizzle as close to raw SQL as I can (I use the query builder not their
db.queryDrizzle's functions are fine for simple queries. Any more advanced and they're messy and limited
WLuckily most queries usually are simple
Pdoes D1 have "varbinary"? also where can i find a list of all the types?
WIYeah and then you can use the raw API for anything that doesn't fit in the simple query builder pattern.
IOr just use the driver directly I guess :lul:
JRaw sql for db usage, drizzle kit for migrations.
GI'm just glad I'm not the only one that prefers raw sql. 
KIām encountering very slow query issue, any way to check why? Already enabled smart place worker
Kquery is simple and datasets are small
Gdoes CAST work in d1 queries?
A@kamama I've reported the same issue yesterday. I guess it's how it is. Maybe it's the free plan.
I've dabbled in trying out different cloud DB solutions as suggested by other members here.
But I've haven't found anything I super like.
I'm gonna continue with D1, and it's slow response times - which I will try to mitigate with the CacheAPI.
I've dabbled in trying out different cloud DB solutions as suggested by other members here.
But I've haven't found anything I super like.
I'm gonna continue with D1, and it's slow response times - which I will try to mitigate with the CacheAPI.
KIf itās because of free to make the performance poor, I can understand that, but at least let us know. Just worry after paid, the performance is still poor
KSeems itās better move to Turso until the issue fixed by Cloudflare team
Gis there any way to view indexes in D1 dashboard?
LI don't think there is any intention to increase the overall 10GB limit
TBummer right
K1 query take 224ms (foods_aus raw) and another one take 1.1s (nutrients_aus raw), both enable smart place and under same region
Khow come it have 5x diff..
Kboth records < 10k rows
Mcompare the query
rows_readwrangler d1 insightsi think most of the time consume is on network layer
