Skip to content

Optimization: alloc_objects in sendtables2 #608

@psavelis

Description

@psavelis

Describe the bug
Seems that readFields, qanglePreciseDecoder and noscaleDecoder (at sendtables2) are critical in the reading process and can be probably optimized.

In the Profiling below, we can see the object allocation for those methods:

Image

To Reproduce
Run the parse exporting profiling data (ie.: to pyroscope or generating a flamegraph)

Expected behavior
A clear and concise description of what you expected to happen.

Library version
v5.2.1

Additional context

  • Ran using on MacOS M1 16GB
  • Used Pyroscope to browse and analyze the profiling metrics

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