Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

Thanks Phil, you are correct. Since my last post I converted my db from derby to H2 just to see if it would make a difference and tried the upgrade again and it seems to have worked. Les

This issue can be tracked on GitHub https://github.com/infiniteautomation/ma-core-public/issues/764

Poll times generally indicate the time it takes for the device to respond to all the request for data. The information here probably isn't enough for us to look at especially since we never see this on any other systems so it is quite odd. Generally our modbus networks run at 19.2k baud. You could capture the following system metrics during a time when the polls are slow just to see if something is going wrong on the MangoES: logs/ma.log file Screen shot from the Internal Metrics tab and work items tab Download JSON from the Threads tab on logging console Screenshot of running "top" in a ssh console JSON export of your Modbus Serial Data source and data points so we can review all the settings. These items will help us see if any kind of performance in Mango is causing your poll times to slow down. Thanks,