C
C
I
E
A
WEWWWEWEWWWEA
K
KK
T
DT
J
K
P
C4 Duration is billed in wall-clock time as long as the Object is active, but is shared across all requests active on an Object at once. Once your Object finishes responding to all requests, it will stop incurring duration charges. Calling accept() on a WebSocket in an Object will incur duration charges for the entire time the WebSocket is connected. If you prefer, use state.acceptWebSocket() instead, which will stop incurring duration charges once all event handlers finish running.
5 Duration billing charges for the 128 MB of memory your Durable Object is allocated, regardless of actual usage. If your account creates many instances of a single Durable Object class, Durable Objects may run in the same isolate on the same physical machine and share the 128 MB of memory. These Durable Objects are still billed as if they are allocated a full 128 MB of memory.
CPCif they all do in practice not occupy more than that?
PCDuration billing charges for the 128 MB of memory your Durable Object is allocated, regardless of actual usage
PCPC
NN
KKKKCKC
import * as assert from 'node:assert';
const scores = await fetch('./scores.json');
const data = await scores.json() as any;
assert('weights' in data, `Failed to get weight data of scores.json`);
assert('max_scores' in data, `Failed to get max scores data of scores.json`);
export const WEIGHTS: { [key: string]: number; } = Object.freeze(data['weights']);