Skip to content

Commit

Permalink
Update performance baselines
Browse files Browse the repository at this point in the history
Set `maxRegression` to 1ms for all tests, as it turns out that both the
absolute and relative thresholds must be hit for a perf test to fail.

Update all baselines to the performance of current master. In most cases this
is faster than the previous baseline for Swift tests (often significantly
slow). A bunch of baselines were also previously missing entirely, and we had
some baselines for a target which doesn't even exist in the project any more.

The following tests had their baselines made slower:

Realm.testDeleteAll, Realm.testQueryDeletion, RealmSwift.testQueryDeletion:
These were made slower by adding more classes which link to the objects being
deleted, and basically all of the time is spent updating backlinks.

Realm.testRealmCreationCached, RealmSwift.testRealmCreationCached: Made slower
by the robust interprocess mutex change.

RealmSwift.testCountWhereTableView: Not sure why this is slower. Profiler says
~90% of the runtime is in the single call to `Query::find_all()`, so it's not
due to binding changes.

Some of the KVO tests were modified because it turned out that they were
actually mostly just benchmarking how long it takes to create an RLMArray,
which got slower due to the change to make LinkList destruction thread-safe.
  • Loading branch information
tgoyne committed May 11, 2016
1 parent 22ff116 commit 0f83ca6
Show file tree
Hide file tree
Showing 9 changed files with 1,222 additions and 698 deletions.

This file was deleted.

Loading

0 comments on commit 0f83ca6

Please sign in to comment.