CircleCI-Public / browser-tools-orb

Quickly and easily install common browsers and browser testing tools on CircleCI
https://circleci.com/developer/orbs/orb/circleci/browser-tools
MIT License
24 stars 34 forks source link

Installing default latest version running ~1.6x longer than specifying identical version #103

Open prpetten opened 9 months ago

prpetten commented 9 months ago

Orb version

1.4.6

What happened

Running with specified version Across 24 executions (2 runs with 12 parallelism) [resource_class: medium] averaged an install time of 8.75 seconds

Executing

      - browser-tools/install-chrome:
          chrome-version: 121.0.6167.139
          replace-existing: true

Output

Google Chrome is not currently installed; installing it
Preparing Chrome installation for Debian-based systems
2024-02-01 21:56:41 URL:https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_121.0.6167.139-1_amd64.deb [106447036/106447036] -> "/tmp/chrome.deb" [1]
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'google-chrome-stable' instead of '/tmp/chrome.deb'
The following NEW packages will be installed:
  google-chrome-stable
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/106 MB of archives.
After this operation, 339 MB of additional disk space will be used.
Get:1 /tmp/chrome.deb google-chrome-stable amd64 121.0.6167.139-1 [106 MB]
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package google-chrome-stable.
(Reading database ... 41230 files and directories currently installed.)
Preparing to unpack /tmp/chrome.deb ...
Unpacking google-chrome-stable (121.0.6167.139-1) ...
Setting up google-chrome-stable (121.0.6167.139-1) ...
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/x-www-browser (x-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/gnome-www-browser (gnome-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/google-chrome (google-chrome) in auto mode
Processing triggers for mime-support (3.64ubuntu1) ...

Running with no specified version Across 24 executions (2 runs with 12 parallelism) [resource_class: medium] averaged an install time of 14.25 seconds

Executing

      - browser-tools/install-chrome

Output

Google Chrome is not currently installed; installing it
Preparing Chrome installation for Debian-based systems
OK
Installing Chrome for AMD64
Get:1 http://dl.google.com/linux/chrome/deb stable InRelease [1825 B]
Get:2 http://archive.ubuntu.com/ubuntu focal InRelease [265 kB]                
Get:3 https://deb.nodesource.com/node_18.x focal InRelease [4583 B]            
Get:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]        
Get:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]      
Get:6 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1080 B]
Get:7 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]      
Get:8 http://archive.ubuntu.com/ubuntu focal/restricted amd64 Packages [33.4 kB]
Get:9 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages [1275 kB]     
Get:11 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages [177 kB]
Get:12 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [11.3 MB]
Get:13 https://deb.nodesource.com/node_18.x focal/main amd64 Packages [776 B]  
Get:10 https://packagecloud.io/github/git-lfs/ubuntu focal InRelease [28.0 kB] 
Get:14 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [3345 kB]
Get:15 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [32.4 kB]
Get:16 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [3807 kB]
Get:17 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [1469 kB]
Get:18 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 Packages [55.2 kB]
Get:19 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 Packages [28.6 kB]
Get:20 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [3330 kB]
Get:21 https://packagecloud.io/github/git-lfs/ubuntu focal/main amd64 Packages [3505 B]
Get:22 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [1172 kB]
Get:23 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [3196 kB]
Get:24 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 Packages [29.7 kB]
Fetched 29.9 MB in 2s (16.0 MB/s)                             
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  google-chrome-stable
0 upgraded, 1 newly installed, 0 to remove and 104 not upgraded.
Need to get 106 MB of archives.
After this operation, 339 MB of additional disk space will be used.
Get:1 http://dl.google.com/linux/chrome/deb stable/main amd64 google-chrome-stable amd64 121.0.6167.139-1 [106 MB]
Fetched 106 MB in 1s (126 MB/s)                
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package google-chrome-stable.
(Reading database ... 41230 files and directories currently installed.)
Preparing to unpack .../google-chrome-stable_121.0.6167.139-1_amd64.deb ...
Unpacking google-chrome-stable (121.0.6167.139-1) ...
Setting up google-chrome-stable (121.0.6167.139-1) ...
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/x-www-browser (x-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/gnome-www-browser (gnome-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/google-chrome (google-chrome) in auto mode
Processing triggers for mime-support (3.64ubuntu1) ...
Google Chrome 121.0.6167.139  has been installed to /usr/bin/google-chrome-stable

Expected behavior

I would have expected slightly longer install time to make a quick query to get the latest version, and then run an identical install. However, taking 60% longer was not expected. It looks like it is running different processes that could probably be optimized by getting the latest version number, and then following an identical install.