Resource usage - Revision history

Lara at 14:38, 14 November 2024

2024-11-14T14:38:29Z

Simonglm: moved sentence above the table

2021-11-22T14:31:15Z

moved sentence above the table

Simonglm: /* MQTT Packet */

2021-11-22T14:28:57Z

MQTT Packet

Simonglm: /* Network Resources */

2021-11-22T14:00:34Z

Network Resources

Simonglm: /* CPU */

2021-11-22T13:32:38Z

CPU

Simonglm: removed non-descript header text in table header

2021-03-25T19:31:30Z

removed non-descript header text in table header

Simonglm: /* Network Resources */ Typo

2021-02-02T21:10:51Z

Network Resources: Typo

Simonglm: Simonglm moved page Connectivity to Resource usage: Rename for more info on one page

2021-01-31T01:14:13Z

Simonglm moved page Connectivity to Resource usage: Rename for more info on one page

Simonglm: Restructuring for more comprehensive info on Resources in the future

2021-01-31T01:12:14Z

Restructuring for more comprehensive info on Resources in the future

Simonglm: /* Used Ports */

2021-01-29T14:05:48Z

Used Ports

@@ Line 2: / Line 2: @@
 === CPU ===
 The majority of CPU utilization associated with the muondetector-daemon is due to the signal transfer to and from the MuonPi HAT via the GPIO-pins. As of [https://github.com/MuonPi/muondetector/releases/tag/v2.0.2 v2.0.2], this is handled by the "pigpiod" process, which takes about 20% of the processor time according to [[wikipedia:top (software)|top]]. The muondetector-daemon itself, uses only ~2%.
 == Network Resources ==

@@ Line 55: / Line 55: @@
 | '''Total''' || '''150 byte'''
 |}
 Example data of multiple MQTT packets being send to our servers:
@@ Line 167: / Line 170: @@
 | muonpi/log/user/0 || 2021-01-26_22-08-43 || vsense                  || 0.2405174     || V      || Voltage across sensing resistor
 |}

@@ Line 34: / Line 34: @@
 === MQTT Packet ===
-Detector telemetry and mesurement data is send to our servers via the MQTT protocol.
+Detector telemetry and measurement data is send to our servers via the MQTT protocol.
 Upon receiving a MQTT message from the client our servers respond with an MQTT acknowledgment packet which is in turn acknowledged by the client.
-Generally two types of MQTT messages are send, the event message and the log message.
+Generally two types of MQTT messages are sent: the event message and the log message.
 The event messages consist of the following:
 {| class="wikitable"
@@ Line 55: / Line 56: @@
 |}
-The log messages consist of multiple MQTT messages packed into a single (sometimes two seperate) TCP packets
+Example data of multiple MQTT packets being send to our servers:
 {| class="wikitable"
 |-
 ! # !!MQTT topic !! timestamp (rising edge) !! timestamp (falling edge) !! - !! Event counter !! - !! - !! -
 |-
-| 1 || muonpi/data/user/0 || 1611698307.895514697 || 1611698307.895515885 || 70 || 35109 || 1 || 2 || 1
+| 1 || muonpi/data/<user>/<detectorID> || 1611698307.895514697 || 1611698307.895515885 || 70 || 35109 || 1 || 2 || 1
 |-
-| 2 || muonpi/data/user/0 || 1611698307.912153060 || 1611698307.912154247 || 70 || 35110 || 1 || 2 || 1
+| 2 || muonpi/data/<user>/<detectorID> || 1611698307.912153060 || 1611698307.912154247 || 70 || 35110 || 1 || 2 || 1
 |-
-| 3 || muonpi/data/user/0 || 1611698308.237550951 || 1611698308.237552160 || 70 || 35111 || 1 || 2 || 1
+| 3 || muonpi/data/<user>/<detectorID> || 1611698308.237550951 || 1611698308.237552160 || 70 || 35111 || 1 || 2 || 1
 |-
-| 4 || muonpi/data/user/0 || 1611698308.404480192 || 1611698308.404481380 || 70 || 35112 || 1 || 2 || 1
+| 4 || muonpi/data/<user>/<detectorID> || 1611698308.404480192 || 1611698308.404481380 || 70 || 35112 || 1 || 2 || 1
 |-
-| 5 || muonpi/data/user/0 || 1611698308.699026112 || 1611698308.699027299 || 70 || 35113 || 1 || 2 || 1
+| 5 || muonpi/data/<user>/<detectorID> || 1611698308.699026112 || 1611698308.699027299 || 70 || 35113 || 1 || 2 || 1
 |-
-| 6 || muonpi/data/user/0 || 1611698309.048519516 || 1611698309.048520724 || 70 || 35114 || 1 || 2 || 1
+| 6 || muonpi/data/<user>/<detectorID> || 1611698309.048519516 || 1611698309.048520724 || 70 || 35114 || 1 || 2 || 1
 |-
-| 7 || muonpi/data/user/0 || 1611698309.133318449 || 1611698309.133319657 || 70 || 35115 || 1 || 2 || 1
+| 7 || muonpi/data/<user>/<detectorID> || 1611698309.133318449 || 1611698309.133319657 || 70 || 35115 || 1 || 2 || 1
 |}
 ==== Log message ====
-The log message contains various meta data about your MuonPi setup.
+The log message contains various metadata about your MuonPi setup.
-Example log message:
+An exemplary log message along with a description of each entry:
 {| class="wikitable"
 |-
@@ Line 105: / Line 109: @@
 | muonpi/log/user/0 || 2021-01-26_22-08-43 || freqAccuracy            || 265.0000000   ||  ps/s              ||
 |-
-| muonpi/log/user/0 || 2021-01-26_22-08-43 || geoHash                 || u0ypy122vb    ||                    || GeoHash
+| muonpi/log/user/0 || 2021-01-26_22-08-43 || geoHash                 || u0ypy122vb    ||                    || [[wikipedia:GeoHash|GeoHash]]
 |-
 | muonpi/log/user/0 || 2021-01-26_22-08-43 || geoHeightMSL            || 177.8400000   || m      || Height above mean sea level
@@ Line 161: / Line 165: @@
 | muonpi/log/v/0 || 2021-01-26_22-08-43 || vbias                   || 31.6119833    || V      || SiPM bias voltage
 |-
-| muonpi/log/user/0 || 2021-01-26_22-08-43 || vsense                  || 0.2405174     || V      || Voltage accross sensing resistor
+| muonpi/log/user/0 || 2021-01-26_22-08-43 || vsense                  || 0.2405174     || V      || Voltage across sensing resistor
 |}
-The only privacy sensitive information contained in these messages are the geolocation and ambient temperature. (ellaborate in [[Privacy]])
+The only privacy sensitive information contained in these messages are the geolocation and ambient temperature. (elaborate in [[Privacy]])

@@ Line 7: / Line 7: @@
 == Network Resources ==
 === Data rate ===
 The MuonPi detector board will send measurement data to our data evaluation servers, the rate of which greatly depends on the exact event rate.
@@ Line 15: / Line 18: @@
 [[File:Muonpi-packetsize.png|thumb|Histogram of packet sizes over 45minutes]]
-=== Used Ports ===
+=== Outgoing Ports ===
 {| class="wikitable"
 |-
-! Port !! Application
+! Source Port !! Purpose !! Destination
 |-
-| 8888 || pigpiod
+| muonpi:51508 || GUI connection to other machine on network || othermachine:39830
 |-
-| 1883 (out) || MQTT message publish
+| muonpi:41930 || MQTT message publishing to muonpi.org || muonpi.org:1883
 |}
 === MQTT Packet ===
 Detector telemetry and mesurement data is send to our servers via the MQTT protocol.
-Upon receiving a MQTT message from the client our servers respond with an MQTT acknowledgment packet which is in turn acknowledged by the client with a short TCP message.
+Upon receiving a MQTT message from the client our servers respond with an MQTT acknowledgment packet which is in turn acknowledged by the client.
 Generally two types of MQTT messages are send, the event message and the log message.

@@ Line 1: / Line 1: @@
 == Hardware Resources ==
 === CPU ===
 === RAM ===
 === Disk I/O ===

@@ Line 9: / Line 9: @@
 In a proper setup these messages will average out to roughly 600 messages per minute with an average size of 110 bytes.
 This however includes the acknowledgement packets which account for two thirds of the number of packets but they are only small in size (>150 bytes).
-[[File:Muonpi-iorate.png |thumb|Purple:All messages send between the MuonPi unit and muonpi.org <br>
+[[File:Muonpi-iorate.png |thumb|Purple: All messages send between the MuonPi unit and muonpi.org <br>
 Green: Only MQTT publish messages, excluding acknowledgement messages]]
-[[File:Muonpi-packetsize.png|thumb|Histogram of packetsizes over 45minutes]]
+[[File:Muonpi-packetsize.png|thumb|Histogram of packet sizes over 45minutes]]
 === Used Ports ===

← Older revision	Revision as of 01:14, 31 January 2021
(No difference)

@@ Line 16: / Line 16: @@
 {| class="wikitable"
 |-
-! Header text !! Header text
+! Port !! Application
 |-
 | 51508 || GUI connection