Closed julrich closed 7 years ago
The metrics were missing as a result of the container running the scan not having sufficient RAM, resulting in the rendered video being short / empty, and visualMetrics.py
not being able to determine the correct SpeedIndex as a result.
Increased the RAM on the host (switched host, to be precise), and the problem is gone!
I've got problems getting the SpeedIndex metrics (SpeedIndex, FirstVisualChange, LastVisualChange, PerceptualSpeedIndex, VisuallyComplete, VisualComplete85) for our tests.
The page tested is this one: https://kalenborn.typo3.ruhmesmeile.review (with Basic Authentication kalenborn / betatester).
Configuration as follows:
Starting the container like this:
/usr/bin/docker run --volume /path/to/sitespeedio-config.json:/sitespeedio-config.json --volume /path/to/result:/sitespeed.io/sitespeed-result --volume /path/to/budget-config.json:/budget-config.json --workdir /sitespeed.io --rm --privileged --shm-size=1g sitespeedio/sitespeed.io:5.0.0 --config /sitespeedio-config.json https://kalenborn.typo3.ruhmesmeile.review
I've uploaded some results of this configuration. For some reason, the first
-vvv
run I've tried exited with an error, just rerunning netted the uploaded-vvv
result:With
--debug
and-vvv
: https://ruhmesmeile.com/fileadmin/ruhmesmeile.com/fileadmin/20170429-kalenborn.typo3.performance-debug-vvv.tar.gz With-vvv
: https://ruhmesmeile.com/fileadmin/20170429-kalenborn.typo3.performance-vvv.tar.gzThe error when first running with
-vvv
was this one:Maybe you can glean something from those?