https://github.com/erikdoe/ocmock-profiling
Projects to profile performance issues in OCMock
https://github.com/erikdoe/ocmock-profiling
Last synced: 2 months ago
JSON representation
Projects to profile performance issues in OCMock
- Host: GitHub
- URL: https://github.com/erikdoe/ocmock-profiling
- Owner: erikdoe
- License: apache-2.0
- Created: 2015-09-30T18:25:00.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2016-07-26T22:13:00.000Z (over 9 years ago)
- Last Synced: 2025-03-16T21:22:07.524Z (9 months ago)
- Language: Objective-C
- Homepage:
- Size: 707 KB
- Stars: 2
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# ocmock-profiling
Projects to profile OCMock
## iOSProfileProject
**UPDATE:** As of iOS 9.3 the problems seems to have been resolved in the runtime and the iOS version is as fast as the OS X version again.
Simply run the project in the profiler. There are no unit tests or anything. The code that runs the OCMock code is in `[ViewController viewDidLoad]`. The app will display a label when the loop is finished, usually after 5-10s.
In the Profiler look for `setupForwarderForClassMethodSelector` as an entry point. Ultimately, the vast majority of time is spent in `cache_erase_nolock` from `libobjc.A.dylib`.
## OSXProfileProject
Same story as with iOSProfileProject. For the same number of iterations it is way faster than the iOS version, though; just over 500ms.
The most expensive (in terms of performance) is `cache_eraseImp_nolock` from `libobjc.A.dylib`.