Skip to content

Measure performance impact of recent async changes #444

Open
@radekmie

Description

@radekmie

While getting ready for Meteor 3.0, we've done a lot of internal changes (#412, #413, #424, #428; soon also one for #443). Most of them are simply adding on top of the existing logic to support Promises virtually everywhere; some are actual redesigns (e.g., shape of _scopeBindings).

Of course, adding more logic always comes with a cost, and we should check, whether it's acceptable. So far we didn't hear about any visible regressions, but it should be checked nevertheless.

It's strongly connected to #383, since the majority of the benchmarks should remain synchronous-only, so we could compare the results with previous versions.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

Being worked on

Relationships

None yet

Development

No branches or pull requests

Issue actions