Avoid excessive memory allocation in CvdVideoFrameBuffer webRTC is spending a lot of time in cuttlefish::CvdVideoFrameBuffer::CvdVideoFrameBuffer according to 'perf top -p `pidof webRTC` -K'. The constuctor allocates memory for std::vectors that hold YUV data. Add a simple memory pool that recycles vectors and thus avoids excessive memory allocation. Example CPU utilization without pool: 12.62% webRTC [.] cuttlefish::CvdVideoFrameBuffer::CvdVid... 7.69% webRTC [.] vp8_denoiser_filter_sse2 Example CPU utilization with pool: 8.81% webRTC [.] vp8_denoiser_filter_sse2 5.74% webRTC [.] vp8_copy_mem8x8_mmx Test: Play youtube videos Change-Id: Ie37b0820cfe9881237cbcef957ff6cbca1fbf186
Make sure virtualization with KVM is available.
grep -c -w "vmx\|svm" /proc/cpuinfo
This should return a non-zero value. If running on a cloud machine, this may take cloud-vendor-specific steps to enable. For Google Compute Engine specifically, see the GCE guide.
Download, build, and install the host debian package:
git clone https://github.com/google/android-cuttlefish cd android-cuttlefish debuild -i -us -uc -b sudo dpkg -i ../cuttlefish-common_*_amd64.deb || sudo apt-get install -f sudo reboot
The reboot will trigger installing additional kernel modules and applying udev rules.
Go to http://ci.android.com/
Enter a branch name. Start with aosp-master if you don‘t know what you’re looking for
Navigate to aosp_cf_x86_64_phone and click on userdebug for the latest build
Click on Artifacts
Scroll down to the OTA images. These packages look like aosp_cf_x86_64_phone-img-xxxxxx.zip -- it will always have img in the name. Download this file
Scroll down to cvd-host_package.tar.gz. You should always download a host package from the same build as your images.
On your local system, combine the packages:
mkdir cf cd cf tar xvf /path/to/cvd-host_package.tar.gz unzip /path/to/aosp_cf_x86_64_phone-img-xxxxxx.zip
Launch cuttlefish with:
$ HOME=$PWD ./bin/launch_cvd
$ HOME=$PWD ./bin/stop_cvd
You can use adb to debug it, just like a physical device:
$ ./bin/adb -e shell
You can use the TightVNC JViewer. Once you have downloaded the TightVNC Java Viewer JAR in a ZIP archive, run it with
$ java -jar tightvnc-jviewer.jar -ScalingFactor=50 -Tunneling=no -host=localhost -port=6444
Click “Connect” and you should see a lock screen!