Operations that touch the entire satellite file database can be slow on some machines especially with large databases.
As an example, my EEE pc with 1.6Ghz Atom and 2 Gigs of ram, a tle update can take several minutes and opening the new module or module configuration dialog can take an uncomfortably long time. (Yes, this machine is a little slow these days.)
This should be addressed before importing the satellite catalog from celestrak is implemented as the catalog can add launch date and decay date information on everything NORAD has published publicly. This would instantly bloat most users databases to the same size of extra large.
The correct solution is unclear. A single key file with all satellite data might make sense. Using another database may as well.
The ostrich algorithm and moore's law may also apply.
Log in to post a comment.