Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run Tracker+Archiving benchmarks comparing 2.0 vs 1.12 #4130

Closed
mattab opened this issue Sep 6, 2013 · 1 comment
Closed

Run Tracker+Archiving benchmarks comparing 2.0 vs 1.12 #4130

mattab opened this issue Sep 6, 2013 · 1 comment
Assignees
Labels
Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Sep 6, 2013

Compare 1.12 with 2.0 and look for performance regression:

  • Compare Tracker high concurrency use case
  • Compare Archiving for high traffic days

For this, there are good tools:

  • Benchmark test cases in tests/PHPUnit/Benchmarks give us a time metric (we can spot if something got very slow in 2.0)
  • XHProf report (letting us spot if any new function is called too many times, etc.)
  • It would be great to add XHProf to travis build, exporting the hxprof report for this build to builds-artifacts.piwik.org
@mattab
Copy link
Member Author

mattab commented Dec 26, 2013

Basic tests were done during development & We will do more tests in the future

@mattab mattab added this to the 2.0.3 - Piwik 2.0.3 milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

2 participants