akxcv/vuera

Benchmark

Open

#16 opened on Oct 14, 2017

View on GitHub
 (14 comments) (0 reactions) (0 assignees)JavaScript (4,260 stars) (264 forks)batch import
good first issuehelp wanted

Description

I'm eager to optimise this library, to make it perform as fast as possible, and I already have some thoughts about how to do that. Before optimising anything, though, it's necessary to have a benchmark of the library.

I've been thinking of forking js-framework-benchmark and adding some benchmarks for vuera to the fork.

I'm not sure, though, what exactly we should measure, and I don't know when I'll find the time to do this, so if anyone wishes to help, this is very appreciated.

Contributor guide

Tech stack
javascriptreactvue
Domain
performance
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic knowledge of Vue and ReactUnderstanding of benchmarking methodologiesFamiliarity with js framework benchmark
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue suggests forking the js framework benchmark repository and adding benchmarks specific to vuera. The first step would be to set up the benchmark environment and decide which metrics to measure (e.g., rendering speed, memory usage). Look at existing benchmarks in the forked repo to understand the structure. Then implement vuera benchmarks and run them. The results will guide optimization efforts. Check the issue comments for any additional ideas or questions from maintainers.