Messages Received versus Messages Processed

Hello all,

Just wondering what the typical ratio might be for messages received vs messages processed for an ‘average’ user. It seems, though I have no reference, that my ~ 25% rate seems low… I have the --fix flag set in my config and typical results look like:

Jan 31 16:18:07 Rasp-ADSB2 piaware[486]: 6167258 msgs recv’d from dump1090-fa (4638 in last 5m); 6160012 msgs sent to FlightAware
Jan 31 16:23:02 Rasp-ADSB2 piaware[486]: mlat-client(32745): Receiver status: connected
Jan 31 16:23:02 Rasp-ADSB2 piaware[486]: mlat-client(32745): Server status: synchronized with 337 nearby receivers
Jan 31 16:23:02 Rasp-ADSB2 piaware[486]: mlat-client(32745): Receiver: 1049.1 msg/s received 258.4 msg/s processed (25%)
Jan 31 16:23:02 Rasp-ADSB2 piaware[486]: mlat-client(32745): Server: 0.8 kB/s from server 0.1kB/s TCP to server 2.9kB/s UDP to server
Jan 31 16:23:02 Rasp-ADSB2 piaware[486]: mlat-client(32745): Results: 383.6 positions/minute
Jan 31 16:23:02 Rasp-ADSB2 piaware[486]: mlat-client(32745): Aircraft: 47 of 83 Mode S, 91 of 132 ADS-B used
Jan 31 16:23:07 Rasp-ADSB2 piaware[486]: 6171928 msgs recv’d from dump1090-fa (4670 in last 5m); 6164682 msgs sent to FlightAware
Jan 31 16:28:07 Rasp-ADSB2 piaware[486]: 6176381 msgs recv’d from dump1090-fa (4453 in last 5m); 6169135 msgs sent to FlightAware
Jan 31 16:33:07 Rasp-ADSB2 piaware[486]: 6180610 msgs recv’d from dump1090-fa (4229 in last 5m); 6173364 msgs sent to FlightAware

Should I be concerned with the 25% average or had I better look for issues somewhere?

All the best,

Bob

That number is for the MLAT (multilateration) client. (Multilateration (MLAT) - FlightAware)
Mine is normally around 14%. (I probably have more ADS-B aircraft which broadcast their position. Such their messages are not processed by the MLAT client and the number goes down.)

In short: completely normal, nothing to worry about.

Regards

This just reflects the proportion of messages that are actually getting processed at the Python level, mlat-client goes to some effort to set filters such that only interesting messages make it up to the Python level for performance reasons. (For example, Mode S messages from aircraft that are not currently being requested by the server are filtered out early). A low percentage is actually a good thing here…

1 Like

Thanks !! I very much appreciate the rapid reply -

All the best,

Bob

Hello, Folks.
I just created a small program in awk to count and discriminate the messages with position received. it is consistent with the proportion of 25% and I have around 30 position per second in daylight so it means 108000 messages per hour… Are all these messages computed by flightaware?

I don’t understand what you’re counting, or the question you’re asking.

Hello, Again.
When you connect to the port 30003 via telnet, you start to get messages from the dump in SBS1 text format. One kind of these messages is the type 3, that carries the position and altitude of the aircraft. My program counts this number, the number of messages per second that carries position. It is around 25% of all messages. And in my case amounts of 108000 per hour. My question is: do flightaware processes all these 108000 per hour? If yes, why my amount of positions in a day does not reach 300k?