WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Investigate performance improvements #260

@cllns

Description

@cllns

According to https://github.com/KonnorRogers/view-layer-benchmarks, hanami-view is the slowest of the view layer libraries tested (including slower than Rails partials).

We should take a look to see if there's more performance improvements we can make. I don't expect hanami-view to be the fastest view library, since we offer many features other don't have, but I think it's reasonable to get our performance to be similar to Rails partials and Trailblazer cells (which would require a ~2x speed improvement).

I wonder if there's object allocations we can avoid. One idea I had was to skip wrapping exposures in a Part if the user doesn't have their own Part class defined. Maybe there are other opportunities for similar improvements.

Here's some previous work that was done to this same end: #223

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions