I’m wondering whether a busy websocket connection uses significantly more battery on iOS than a sparsely utilized one - or if there is a constant overhead simply for maintaining the connection that dominates. This will inform some architectural decisions. Thanks!
According to this research paper: HTML5 Connectivity Methods and Mobile Power Consumption, you do consume a significant amount of energy maintaining an inactive websocket, because it is sending frequent messages back and forth to keep the connection alive. Ideally, you would send data at an interval where the websocket could utilize power-saving mechanisms such as "Fast Dormancy" or if the data is sent sporadically, use stateless AJAX requests with a self defined polling frequency.