I thought I'd give it a test too just for more results.
With the layer: 60 fps, 11% cpu
Withou the layer: 60fps, 3% cpu
And adding more layers can slow it to a crawl.
The problem, however, is the actual debugger. Switch over to the "Watch" tab in the debugger instead of "Inspect". I can have 30 layers added onto your project and not exceed 1% CPU use. The Inspect tab keeps track of a lot of stuff. It's meant for really detailed display of everything going on under the hood, whereas Watch is a bit closer to an actual gameplay environment. I use Inspect to pick the variables and values I want to watch (with the eyeball) and then just check that stuff in Watch so not everything needs to be accounted for.
Fore reference, Core i7-4770 3.4 GHz, NVidia GT 640 4GB, 32 GB Ram. This was Chrome on Windows 10.
I am using the free version, so checking in watch-tab is not possible.I will try it once I get it full version. So if its true,is it because of an issue in the debugger then.?
I am attaching a screenshot of the debugger report.
Link-h t t p s : / / w w w .dropbox.com/s/9g55o1lpghsfk8g/Report.PNG?dl=0
Here are my specs,
MY specs are Win7,CORE i5 2500K —,8 GB RAM,Nvidia GTX 560