The tableview is refreshing as new values are received, which is multiple times per second. This breaks scrolling. The logs sections will also become very long, very quickly.
To address the volume, would probably be better to have a single 'logs' cell with a running count, which updates in realtime. Tapping the cell opens a dedicated view for all logs. This consolidation could kick in only after 10 logs have been received.
For scrolling, consider queueing the changes and refreshing the tableview once every second or two. Alternatively, use a UITextView and more of a 'console' metaphor.
The tableview is refreshing as new values are received, which is multiple times per second. This breaks scrolling. The logs sections will also become very long, very quickly.
To address the volume, would probably be better to have a single 'logs' cell with a running count, which updates in realtime. Tapping the cell opens a dedicated view for all logs. This consolidation could kick in only after 10 logs have been received.
For scrolling, consider queueing the changes and refreshing the tableview once every second or two. Alternatively, use a UITextView and more of a 'console' metaphor.