arc_camera_serv starting too early during boot, potentially affecting boot performance |
||
Issue descriptionAccording to a boot chart taken recently, arc_camera_serv starts very early: https://drive.google.com/open?id=1mMrr-K_9d5Mh95YG8UBOEkk0YWXijwNT In fact, arc-camera.conf has "start on starting boot-services". Only stuff that is necessary to render the login screen is OK to start at that point, everything else should be delayed to login-prompt-visible or system-services. Assigning to yusukes@ who last updated the start stanza in https://chrome-internal.git.corp.google.com/chromeos/cheets-scripts/+/fb101e988e8aa6e6dd15666c38b36db984a4c347
,
Nov 9 2017
I'm going to fix this once b/65548422 is resolved. Currently, we have two ways to start the container: 1) start mini container then upgrade later, and 2) start full container without using mini. The problem here is that both uses the same OCI definition (json) file. Even though the mini container never uses the camera, the container still needs the camera's directory because the json file refers to it. For this reason, we wanted to execute the pre-start section of the job at the early stage. We're killing the second way in b/65548422, and once it's done, we can simplify our json file and remove the camera directory from the file. I don't think this affected the boot time (we monitored BootPerf results and didn't see anything) but yes this looks weird and should be addressed. |
||
►
Sign in to add a comment |
||
Comment 1 by jcliang@chromium.org
, Nov 9 2017