globalizejs/globalize

Performance tests

Open

#274 opened on Jun 10, 2014

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (4,759 stars) (645 forks)batch import
help wantednew feature

Description

Goal

  • Test the performance impact of fixes/changes. So, we ensure our performance is continuously improved; #397
  • Compare the performance of Globalize vs. its competitors, so we ensure our performance is good compared to the market;

Workloads

  • TODO (should reflect what Globalize applications look like)

Implementation Ref: https://github.com/jquery/sizzle/tree/master/speed

Some other stuff to evaluate:

Contributor guide

Tech stack
javascript
Domain
performancetesting
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
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.
needs investigation
Prerequisites
JavaScript proficiencyunderstanding of performance benchmarkingfamiliarity with CI/CD
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Review the linked references (e.g., Sizzle speed tests, topcoat benchmarks, perfjankie) and existing test infrastructure in the Globalize repository. Determine a suitable benchmarking framework and define specific workloads that reflect real world Globalize usage. Consult maintainers on desired scope and acceptance criteria before implementing.