@Dean @sz19 @Shannor can you share database IDs of the dbs where you're experiencing the issues?
@Dean @sz19 @Shannor can you share database IDs of the dbs where you're experiencing the issues?
D1_ERROR: D1 DB storage operation exceeded timeout which caused object to be reset.. This happens rarely, but has been happening for weeks and when it happens no request is able to query the database. It seems like it randomly freezes for 30s and then returns that error8a298455-ac11-4e0c-b160-4db807cf3572it also seems like we get the error but the DB action still happensThis part seems incredibly concerning...?

--remote set to true. Should I be concerned about this happening in production, or is it just a dev env issue?
My company intends to use D1 in a system where has write-heavy burst loadsWithout some numbers, and ideally benchmarking your exact use-case and the queries you will run yourself, nobody can confirm if this use-case is suitable for D1. What kind of bursts, how long do they last, how often, what is peak write qps, what are your queries...
D1_ERROR: D1 DB storage operation exceeded timeout which caused object to be reset.8a298455-ac11-4e0c-b160-4db807cf3572D1 is using SQLite Durable Objects, so only 1 query is executed at a specific point in time, but depending on your queries you can get hundreds/maybe low-thousands per second if they are small enough. const [total_records, users] = await Promise.all([
prisma.user.count({
where: whereClause
}),
prisma.user.findMany({
take: limit || undefined,
skip: page && limit ? (page - 1) * limit : undefined,
where: whereClause,
orderBy: sort ? getOrderBy(sort) : undefined,
select: {
id: true,
first_name: true,
last_name: true,
role: {
select: { name: true }
},
email: true,
transportist: { select: { phone: true, status: true } },
cargo_giver: { select: { phone: true, status: true } },
created_at: true
}
})
])