I am used to tile engines for creation of backgrounds and "rooms". Tile engines are efficients, memory and display wise, it only displays the part of the tilemap that is on screen, so you can build a 1000x1000 map if you want and there should be no slowdown.
I know construct doesn't have one (yet) and aims more for a free-form engine where the background is created with sprites (a la Aquaria)
My question s: how efficient is it?
How are the sprites that are not on screen managed? are they all 'ticked' even when not on screen?
How many sprites can I use for a background before the engine starts to slow down?