UNITYCHROMEBOOK HOW TO
UNITYCHROMEBOOK ANDROID
UNITYCHROMEBOOK CODE

See the official usage documentation ⁠ for more information. If you see the GPU times are short and regular, but the CPU times are dominating and causing you to miss frame syncs, take a look at your texture loading/frame preparation algorithms. Although not directly profiling on a ChromeOS device, this should give you information about where your game is spending most of its time each frame, and can give you insight into specifically which GPU calls are being used.įor example, if you see that a large amount of time is being spent in your anisotropic GPU filters and it is dominating the work being done each frame, you can likely make some large performance gains by changing this setting.

Snapdragon Profilerīecause your games behaviour will be the same across devices, one good way to get detailed performance information is to use the Snapdragon Profiler ⁠ on a Qualcomm based, ARM phone. Unity’s profiler has various Profiler Modules ⁠ such as rendering, memory, CPU usage, and physics to get deeper insight into performance on those areas. Included on the page are specific setup instructions for ChromeOS devices ⁠. If your game is built in Unity, then we recommend using their built-in profiler ⁠. This tool does not grant real insight into GPU usage nor into what is happening between each frame sync so, while a good tool to have in the toolbox, is likely not going to be sufficient to get your game running at peak performance.

UNITYCHROMEBOOK CODE

Simple CPU traces can be a quick way to isolate areas of code to look at.

UNITYCHROMEBOOK ANDROID

From Android Studio, instead of hitting “Run”, simply choose “Profile” to run your app and get real-time insight into CPU, memory, and network usage.

The easiest way to start profiling any Android app is with the integrated Android Studio profiler ⁠. There are many tools out there, but here are some of our go-to programs. While it’s certainly possible to determine bottlenecks on your own, having the right tools will make analyzing your game’s performance easier and will give you confidence that you’re focusing on the right things.

UNITYCHROMEBOOK HOW TO

A desktop game that assumes GPU filters are fast, may find integrated GPUs taking too long to render each scene.įor more details on how to approach profiling, check out ARM’s guide on ‘The optimization process’ ⁠. Remember that many mobile phones and ChromeOS devices do not have discrete graphics cards. Instead, if you are using a large number of detailed, GPU based filters, your game is likely GPU-bound. For example, if it is taking a long time calculating and loading the vertices before the GPU begins rendering, your game may be CPU-bound. Using the profiling tips and tools below, attempt to determine where the system is “spending it’s time” each frame. In most cases, games will show themselves to either be “CPU-bound” or “GPU-bound”. If you are new to profiling, a good general approach is to: Improving the algorithm will improve the game on all devices. For example, an inefficient texture loading algorithm may “work fine” on higher end mobile devices, but not be able to keep up on a Chromebook with a 4k display. ChromeOS, with a tendency for larger displays and desktop input devices, may just surface certain issues more readily. Something to keep in mind when specifically optimizing your game’s performance on ChromeOS is that the underlying performance issues are shared across all devices, and improvements will benefit performance and battery life for all users. Below are some tips to help speed up the process. On ChromeOS, many tools are designed with ARM chipsets in mind. The many moving parts that need to be perfectly synchronized in a game combined with the complexity in a given scene can make understanding and isolating problems difficult.

Performance profiling and tuning is a complex task that can feel more like an art than a science.

Unitychromebook