search

realm / realm-core

Core database component for the Realm Mobile Database SDKs
https://realm.io
Apache License 2.0
1.02k stars 158 forks source link

Performance Tests Roadmap #1573

Closed oleks closed 7 years ago

oleks commented 8 years ago
  1. Get up to speed with the existing benchmarks, hereunder fix compilation problems, clean up the code, and provide some documentation.
    • [ ] benchmark-common-tasks
      • Now works, see #1596.
    • [ ] benchmark-common-tasks-ios
  2. Check out celero.

Maybe later:

Stack (motivated by @emanuelez):

Meeting 2016-04-14:

  1. Measure new date-time performance
  2. Make it visible
    • Data collection
    • Collect and plot all data, don't summarize prematurely.
    • Presentation
  3. Make what we measure reliable
    • Show delta warnings in PRs
  4. Measure the right thing
    • Hardware: Use the Raspberry Pis.
    • Method: Try Celero
simonask commented 8 years ago

So we should definitely think about prioritization here, because I don't think all of those benchmark suites are equally important, and there are several interesting ones that we don't have a benchmark for today at all. But getting stuff, anything, up and running is a great start!

oleks commented 8 years ago

Minutes from the meeting on 2016-04-14:

  1. Measure new date-time performance
  2. Make it visible
    • Data collection
    • Collect and plot all data, don't summarize prematurely.
    • Presentation
  3. Make what we measure reliable
    • Show delta warnings in PRs
  4. Measure the right thing
    • Hardware: Use the Raspberry Pis.
    • Method: Try Celero
ironage commented 7 years ago

There is now a framework for integration of benchmarks into PR workflow in #2368. It has support for benchmark-common-tasks and benchmark-crud and presentation of results. I believe this addresses points 2, 3, and 4 of the requirements in this issue. Benchmarking the Timestamp code can be taken as a separate task if required.