On 11.04.2018 at 06:10:09 UTC the 2.000.000th packet was received by TTNmon. It was sent by this node in Apeldoorn. So it’s time for some stats!
The database currently holds the data of 66 nodes sending their packets to 408 gateways. The packet table grows by about 17.000 packets per day. This table only stores the nodes information like packet time, counter or spreading factor. The main table which holds the link quality for each gateway which heard a packet stores currently 4.540.309 rows. It grows by ~34.000 rows per day.
The packet table has a size of ~185 MB. The table storing link quality has a size of ~490 MB. The total database size including user and device table is about 680 MB which caused TTNmon becoming slow and unstable at my shared hosting provider within a short time after the public launch.
In the beginning I cared less for database and dump size. Starting compressing them during the dump process significantly decreased the dumps size. But as of today even the compressed database dumps reached a size of 100 MB.
When I introduced the Map the data was generated every 10 minutes by a cronjob. Later the cronjob started to hit memory limits. Even the basic job which created a list of all known gateways ran longer than 10 minutes. The job to process the colored links between nodes and gateways ran into timeout. The problem was fixed a few days ago. Now the required information are collected instantly when a new packet is received. This means that the map became more dynamic while the server has lower loads.
As previously mentioned, TTNmon started to hit my hosters limits. Thanks to the support of the TTN Community Aachen and CCCAC I’m able to run TTNmon on a virtual server which provides the required ressources.
Looking forward to 5.000.000 packets which should be reached within the next five to six months.