'Aspects' refers to the groups of objects that are processed by some sub-systems, that is 3D or 2D physics, navmesh, sprites, lighting, scripts and plugins, rendering, GUI, audio, video or particles, etc. In order to find what is adding more complexity, or processing to the scene, you could remove or change 'aspects' of the scene one by one, then profile and see how that affects the Overhead. The Profiler's hierarchy is populated with the processes that are most likely to consume important resources, but lots of hidden tasks will still remain. This means that it is not possible for us to provide statistics on the complexity of the scene since it depends on many factors. Depending on the work performed, this increase could be significant or not. More importantly, the different engine sub-system tasks on those objects (in this case, tasks that are not being actively measured in the Profiler) will be added to this complexity, increasing the Overhead. If you have lots of objects, processing all of them will take more time than just a few. The complexity of the scene does not refer directly to the amount of objects that compose it, but to the processing in general. It also accounts for the vertical synchronization that can be set to a fixed duration with Application.targetFrameRate. The more complex the scene, the more Overhead it will produce. It is usually related to the internal processing of the scene. In the Profiler, the Overhead is the total frame time minus the duration of everything else that is actively measured. I receive memory warnings on target device.I have very complex scenes, or a GPU/CPU bound game.The overhead in my Profiler Window is high.

Filebeats cpu overhead