From ATCSMon Wiki
Jump to navigation Jump to search

At monitoring startup, the application may be connecting to a server with a large packet flushdown, a feature designed to quickly populate the display. If the user experiences a sort of lockup during flushdown, that's pretty common. The application is absorbing much data in a short period. If the user simply waits it out, the performance should return when the flushdown completes. Some flushdowns are getting to be absurdly large due to mega-aggregators, so the wait may be up to a minute, but usually closer to 15 seconds. Test a lesser flushdown server alone, such as the default atcsmon.com:4800 to see if this is your issue.

-- Main.GaryHahn - 31 Aug 2008