Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0p3
Issue ID
945462
Regression
No
[iOS, il2cpp] System.DateTime.Now is slow on the first run
To reproduce:
1. Open project attached by QA
2. Build it for iOS
3. In XCode's top menu bar select Product -> Profile
4. From the instruments select time profiler
5. After opening Time Profiler hit record button
6. Record for ~10seconds.
7. In the timeline find a spike in CPU usage and make selection on this spike
Expected: System.DateTime.Now should take the same amount of time on all the runs
Actual: On the first run it takes more time (is slower)
Reproduced on: 5.6.3f1, 2017.1.1f1, 2017.2.0b10, 2017.3.0a7
Reproduced with: iPhone SE OS 9.3
Comments (4)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- Dragging selector from selector row background shows preview but does not apply class in UI Builder
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
CorryStHaggen
Apr 24, 2022 23:50
Hello. I need help, or at least advice to begin with, about software quality assurance. Who can be contacted with this question?
roointan
Sep 06, 2020 09:01
more info about why this is slow https://stackoverflow.com/a/4075602/1235063
you can use Time.time or a TickCount alternative which doesn't need to query the system time
roointan
Feb 16, 2020 11:50
How is it slow by design??