Investigate increase in "bootup-time" errors
See original GitHub issueawful repro:
N=30
export CHROME_PATH="/Applications/Google Chrome Canary.app/Contents/MacOS/Google Chrome Canary"
mkdir -p timing-runs
for run in {1..$N}
do
echo "run NS $run"
output_path="timing-runs/ns-$run.json"
node lighthouse-cli https://www.elbatal-egypt.com/nader/ --output json --output-path="$output_path" --chrome-flags="--enable-features=NetworkService" --save-assets 2> /dev/null
grep -q "Invalid task timing data" "$output_path"
if [ $? -eq 0 ]; then
echo broke
fi
done
for run in {1..$N}
do
echo "run no NS $run"
output_path="timing-runs/no-ns-$run.json"
node lighthouse-cli https://www.elbatal-egypt.com/nader/ --output json --output-path="$output_path" --chrome-flags="--disable-features=NetworkService" --save-assets 2> /dev/null
grep -q "Invalid task timing data" "$output_path"
if [ $? -eq 0 ]; then
echo broke
fi
done
for trace in timing-runs/*.trace.json; do
echo $trace
grep '"ph":"B"' $trace | wc -l ; grep '"ph":"E"' $trace | wc -l ;
done
Runs 12 and 15 for NS on failed. NS off never failed. Using Canary 75.0.3745.0.
Just NS 12 and 15:
timing-runs/no-ns-1-0.trace.json
11057
11052
timing-runs/no-ns-10-0.trace.json
13173
13168
timing-runs/no-ns-11-0.trace.json
11194
11189
timing-runs/no-ns-12-0.trace.json
10710
10705
timing-runs/no-ns-13-0.trace.json
10992
10986
timing-runs/no-ns-14-0.trace.json
11276
11270
timing-runs/no-ns-17-0.trace.json
10534
10529
timing-runs/no-ns-18-0.trace.json
10845
10839
timing-runs/no-ns-19-0.trace.json
11046
11041
timing-runs/no-ns-2-0.trace.json
9754
9750
timing-runs/no-ns-20-0.trace.json
11345
11339
timing-runs/no-ns-21-0.trace.json
12167
12161
timing-runs/no-ns-22-0.trace.json
11571
11566
timing-runs/no-ns-23-0.trace.json
11784
11778
timing-runs/no-ns-24-0.trace.json
12144
12138
timing-runs/no-ns-25-0.trace.json
12870
12864
timing-runs/no-ns-26-0.trace.json
11549
11543
timing-runs/no-ns-27-0.trace.json
12113
12107
timing-runs/no-ns-28-0.trace.json
11884
11880
timing-runs/no-ns-29-0.trace.json
11580
11574
timing-runs/no-ns-3-0.trace.json
11248
11242
timing-runs/no-ns-30-0.trace.json
11901
11895
timing-runs/no-ns-4-0.trace.json
10796
10790
timing-runs/no-ns-5-0.trace.json
3537
3533
timing-runs/no-ns-6-0.trace.json
11472
11466
timing-runs/no-ns-7-0.trace.json
10895
10890
timing-runs/no-ns-8-0.trace.json
10997
10992
timing-runs/no-ns-9-0.trace.json
10665
10660
timing-runs/ns-1-0.trace.json
12281
12276
timing-runs/ns-10-0.trace.json
11881
11876
timing-runs/ns-11-0.trace.json
12156
12151
timing-runs/ns-12-0.trace.json
8761
8754
timing-runs/ns-13-0.trace.json
12384
12379
timing-runs/ns-14-0.trace.json
11936
11931
timing-runs/ns-15-0.trace.json
12096
12087
timing-runs/ns-16-0.trace.json
4120
4116
timing-runs/ns-17-0.trace.json
11637
11632
timing-runs/ns-18-0.trace.json
11660
11654
timing-runs/ns-19-0.trace.json
12428
12422
timing-runs/ns-2-0.trace.json
11877
11872
timing-runs/ns-20-0.trace.json
10836
10831
timing-runs/ns-21-0.trace.json
11888
11883
timing-runs/ns-22-0.trace.json
11808
11803
timing-runs/ns-23-0.trace.json
12032
12027
timing-runs/ns-24-0.trace.json
11909
11904
timing-runs/ns-25-0.trace.json
11018
11013
timing-runs/ns-26-0.trace.json
11617
11612
timing-runs/ns-27-0.trace.json
11674
11668
timing-runs/ns-28-0.trace.json
12381
12376
timing-runs/ns-29-0.trace.json
14834
14829
timing-runs/ns-3-0.trace.json
11533
11528
timing-runs/ns-30-0.trace.json
12478
12472
timing-runs/ns-4-0.trace.json
12751
12746
timing-runs/ns-5-0.trace.json
11631
11625
timing-runs/ns-6-0.trace.json
11443
11439
timing-runs/ns-7-0.trace.json
11955
11950
timing-runs/ns-8-0.trace.json
12248
12243
timing-runs/ns-9-0.trace.json
11776
11770
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Investigate boot time info error.
Investigate boot time info error. Latest version (5.2.0.5) is giving wildly wrong boot time info. E.g. 8 mins 15 sec, (9 mins +)....
Read more >Tools-and-techniques-for-reducing-bootup-time.ppt - eLinux.org
For older kernels, I have a patch for some ARM platforms: safe_to_call_sched_clock.patch. initcall_debug. A good portion of bootup time is spent in 'initcalls' ......
Read more >Programmatically getting system boot up time in c++ (windows)
The information in question is on the Win32_OperatingSystem object under the LastBootUpTime property. You can examine other properties using WMI Tools.
Read more >Solved: XPS 8910, long boot time - Dell Community
Needless to say, the slow boot-up time issues have now returned. ... No errors are reported, and no reason for the delay found,...
Read more >PME and Windows Update Agent Error Codes - N-able
Investigations with our software seem to show people have only resolved this when a newer set of updates have been released and installed....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
this will not be fast
bisect-timing.sh
mostly fixed in #7728, with more coming in #9230 and tracked in #7764