H
fetch
GG
L
HHH
D
1
user_id
L1
B
MML
PL
PP
const ran = await runDurableObjectAlarm(stub); expect(ran).toBe(true);this.state.getWebSockets
SS
F
FFILWill the DO billing charge for cold-starts etc ?No, you pay only the time after your DO is running.
IF, Workers consumes 10ms (and hence billing time = 10ms) for above simple Use-case, is it "FAIRLY ACCURATE" to assume that the DO will also consume 10ms (and hence billing time = 10ms) for the same Use-case.Assuming that the
10ms@cloudflare/next-on-pagesdurable-utils@0.3.0StaticShardedDOone/some/all()tryOne/trySome/tryAll()tryN(...)StaticShardedDO
IILILConclusion : Workers Compute is 12.5x times COSTLIER than DO-Compute.That's a very unusual conclusion for real world applications. Anyone can do their calculations of course, but please be careful when you compare them otherwise you will be in for not so nice surprises.
II it("adds jobs and schedules an alarm", async () => {
const result = await runInDurableObject(stub, async (instance, state) => {
return await instance.addJobs([
{ url: "https://example.com" },
{ url: "https://example.org" },
]);
});
expect(result).toBe("Jobs added");
// Run the alarm (which calls processQueue & processTimeouts)
const ran = await runDurableObjectAlarm(stub);
expect(ran).toBe(true);
const status = await runInDurableObject(stub, async (instance) => {
return await instance.getStatus();
});
expect(status).toEqual([{ status: "pending", count: 2 }]);
});Durable Object alarms are not reset between test runs and do not respect isolated storage. Ensure you delete or run all alarms with runDurableObjectAlarm() scheduled in each test before finishing the test. afterEach(async () => {
// Clear any pending alarms between tests.
await runInDurableObject(stub, async (_instance, state) => {
await state.storage.deleteAlarm();
});
vi.restoreAllMocks();
});