Helps us to gauge folks' expectations haha
Helps us to gauge folks' expectations haha
HNeeds to be in memory in every edge metal :lul:
EYeah sorry I thought it was obvious myself/rabbit were just speculating, didn't intend any harm from that
HSQLite from Disk, like Fly's LiteFS.
MGlen mentioned something about that a few days back
MWhatever CF ends up doing as far as replicas go, hopefully it'll be flexible. For example, I operate a (relatively speaking) small DB for a volunteer organization which is local to a certain city's metropolitan area. Therefore, we have no need for any kind of replication (as pretty much all requests will hit the same PoP), and we are very cost sensitive, so being able to forgo replication would be a huge plus for us.
Mfeature request for the D1 dashboard interface: when displaying the contents of some table, it'd be really helpful if there was some way to differentiate between a NULL value and a text field which contains an empty string or whitespace, to avoid this situation:
Myeah good point
HI mean, you are still bound by the limits of a DO, so you probably won't get much more than a few 100 rps.
Mpretty sure it'll be there by release, if not sooner
Jd1 Can I have a rough schedule of when this beta or official release will be?
MWe don't give rough schedules, though we announce things like this at developer week or birthday week
Khi, is it possible to beg for a 3x size increase in D1? I'm very eager to try for a prototype, but my biggest table is 173M in sqlite format so I need at least 300M
D
Hi! The current implementation of D1 is limited by the memory limit of Workers/Durable Objects. The docs say that this limit will be increased in the future, I'd say 
KThe docs also say that if I need more then
If your use case requires a larger database, please reach out!Kbut I got the point, alas...
Dthey are gathering feedback, and looking for use cases so they can make sure to support them in GA
EHi, is this normal for D1 to be so slow? I get that it's alpha, but 500ms+ to do a SELECT on a 230KB database? Doing 2 or 3 more SELECT and you're easily 1.5s+ ... sounds like something's wrong here to me
EAnd with local wrangler, same operation is about 1-2 ms
EWhether thats normal depends on a few factors, like where the client is located compared to where the database was first populated/created in, however it has been said that speed is not something thats been looked at very much in this stage of the alpha, and it will get better in the future
W^ remember that local is local
MHopefully D1 gets faster than querying a DB from another cloud
Nwhen i run
insert into user_agent (value) values ('test2') on conflict(value) do nothing returning id the first time i get the id and then for every new request the last row id is bumped and not returned, is this a d1 or sqlite thing?Nand how should i do this logic efficiently, if this isn't the right way?
Nthis is what happens in case of an empty new table, running the above statement:
1) insert
2) insert
3) insert
1) insert
test returns 12) insert
test returns nothing (insertion doesn't happen)3) insert
test1 returns 3Nwell
insert into user_agent (value) values ('test2') on conflict(value) do update set value = excluded.value returning id works, but it feels wrong...
MHave you looked at the docs here? https://developers.cloudflare.com/d1/learning/using-d1-from-pages/
A binding enables your Pages Functions to interact with resources on the Cloudflare developer platform. Use bindings to integrate your Pages Functions …
EI am from Madagascar, and normally there is a Cloudflare Data center here in the capital, but it seems to be not stable at all, or may be incomplete, I have no idea but it's unreliable (sometimes its up, sometimes it's not, and not all services are available there, like there's not WARP). So, the second hop from there is in South Africa (that one is reliable so far). That's about 60ms away.
I assume the DB should be created there. It makes no sense to create it further away.
Now, @Walshy | Pages I agree that local is local, but that should give us a good baseline of how much that operation really costs. With pessimistic estimation, it should be anywhere around 100ms for a single simple SELECT operation, assuming there are much overhead involved, I'd say at most 200ms. Now, 500 - 600ms response time, that's hard to understand why.
While I'm just might skip D1 for this current side project, I hope D1 will live up to the high standards of other Cloudflare products that I really love.
I assume the DB should be created there. It makes no sense to create it further away.
Now, @Walshy | Pages I agree that local is local, but that should give us a good baseline of how much that operation really costs. With pessimistic estimation, it should be anywhere around 100ms for a single simple SELECT operation, assuming there are much overhead involved, I'd say at most 200ms. Now, 500 - 600ms response time, that's hard to understand why.
While I'm just might skip D1 for this current side project, I hope D1 will live up to the high standards of other Cloudflare products that I really love.
HNote that not all Datacenters actually support DOs. As an example, these are the spawn statistics for DOs created from Antananarivo:
MSpeaking of performance, the D1 dash is now optimistically loaded, so you should see significantly fewer loading screens as you navigate around
Mif you're running wrangler to test this, you'll need to add
--persist to keep the data between runs
Jis anyone else having issues creating new backups?
