Skip to content

Baseline JSON against MessagePack throughput and allocations #30

Description

@Agash

Low priority. The library offers two transports and says nothing measurable about the difference, so the choice is currently made on vibes. The serializer paths also changed substantially in the shape audit, and #19 will add an addressing layer on top of them.

Scope

Deliberately narrow: payload serialize and deserialize on both transports, across the response shapes that actually differ — a flat record, a stub list (GetSceneList), and a high-frequency event (InputVolumeMeters). Throughput and allocated bytes per operation.

Not the full nine-workload suite. Batches, event dispatch and request correlation can be added if the first numbers suggest they are interesting; benchmarking them up front produces a project nobody reads.

Baseline only. No optimisation work off the back of it without a reason.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions