NativeScript / NativeScript/android
inconsistency in native class extension duration
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 563
- Forks
- 144
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 14
Description
I am working on perfs and spending a lot of time on profiling timelines.
I see very weird inconsistencies in materializing and native class `extending.
This is 2 different app starts with the same exact code. Globally everything is the same except for those "yellow" times.
Here it is a factor 10 which is pretty big.
I add this mostly to start the discussion on what could be the reason for that and how we can make sure we get the smallest one.
- could that be do to profiling?
- @darind do you have an opinion on this?
- here it is in debug, but i see the same kind in production. The difference might be smaller though i am not sure. Can debug/production make a difference for this?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are named. Start by reproducing two app starts with identical code in debug and production while comparing profiling timelines, and investigate whether profiling or build mode accounts for the materializing and native class extension variance. Done should document the cause and an agreed way to measure or minimize it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp
- Domain
- mobile-dev, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100