Client payload sizes

By Rosedo Devs · 6 months ago

Tranferring state from backend to client has been very greedy so far, passing payloads of over 1MB per evolutionary update, ~60 frames per second. Fine for development, but slow and costly to put into production, where egress costs accumulate and data has to travel over the wire across long physical distances to each client.

Typically you want a single payload to be no more than 1kb, and ideally less than 10kb per second.