access:trackwork_server
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
access:trackwork_server [2009/04/21 23:26] mmatthews |
access:trackwork_server [2012/10/10 17:12] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | [[main|Main Page]] | ||
| ====== Trackwork Server ====== | ====== Trackwork Server ====== | ||
| Line 10: | Line 9: | ||
| After a few weeks of testing with the Vasco Road/Teichert job we are closing in on 3 million GPS | After a few weeks of testing with the Vasco Road/Teichert job we are closing in on 3 million GPS | ||
| data points all in one database table. It makes me wonder how the product will scale if we have | data points all in one database table. It makes me wonder how the product will scale if we have | ||
| - | several of these jobs running in parallel on several system. Since all the GPS data lives in the | + | several of these jobs running in parallel on several systems. Since all the GPS data lives in the |
| database it would be hard if not impossible to rebuild the DB if it were to become corrupt. | database it would be hard if not impossible to rebuild the DB if it were to become corrupt. | ||
| - | We could try and fallback to a backup (are we running backups?). | + | We could try and fallback to a backup (are we running backups)? |
| + | |||
| + | No backups - Mike Clapp | ||
| If we re-implement the server I would think moving to a system where the GPS data was stored | If we re-implement the server I would think moving to a system where the GPS data was stored | ||
| Line 22: | Line 23: | ||
| ===== Performance ===== | ===== Performance ===== | ||
| + | There are several performance issues with the current system mostly surrounding the fact that database access is unbounded. There is no throttling or concept of locking/transactions surrounding the update of data for a single device. I created a bug that caused the server to become overloaded and slow to respond. The TMMs responded by constantly dropping the connection and | ||
| + | trying to reload their data. This caused the server to try and process multiple requests simultaneously from a single device for the exact same data! Suffice to say...this caused some problems. | ||
| - | ===== Compatibility ===== | + | At the very least any re-implementation should take into consideration the following: |
| - | (this may not be the correct spot for this) | + | |
| - | - 64 bit compatibility - Initial testing shows TMM lib doesn't work on 64 bit Vista (UNCONFIRMED, may be operator error) | + | |
| - | - Verify latest version | + | |
| - | - Check to see if Vista has a 32 bit compatibility flag | + | |
| - | - If confirmed, evaluate fix option | + | |
| - | - Trackwork server (tough) | + | |
| - | - Client library settings (32 bit compatibility mode?) | + | |
| - | - Installer options? (if Vista has compatibility mode) | + | |
| - | + | - Throttling of connections so as not to overwhelm the database. | |
| + | - Transaction support in case an operation fails part way through an update | ||
| + | - Transaction/locking support so that multiple operations on the data for a single device are protected. | ||
| + | |||
| + | ===== Compatibility ===== | ||
| + | 64 bit Vista compatibility has tested ok on view and download as of V 2.05C (4-10-09). | ||
| + | * should test upload (G-ray) | ||
| + | |||
| Line 59: | Line 61: | ||
| - Improved log messages | - Improved log messages | ||
| + | ===== Track Server Functions (Current)==== | ||
| + | This is the current Trackwork functionality. It does not have the API functions being called and that should probably be added. These are all currently contained within the Server Tab of the Import dialog with the exception of Upload. | ||
| + | |||
| + | ==== Projects ==== | ||
| + | * Delete Project (RM menu) | ||
| + | * Add (Name, Description(O), Bounds(O), Start Date) | ||
| + | * Modify (Name, Description, Status (inop), Bounds, Start Date) | ||
| + | * Delete Project (Button) | ||
| + | |||
| + | === Potential === | ||
| + | * Partial download of tracks from a single project | ||
| + | |||
| + | ==== Tracks ==== | ||
| + | * Read Tracks | ||
| + | * Download Points (based on selected tracks) | ||
| + | * Delete (RM Menu) | ||
| + | * Move to other Projects) | ||
| + | * Select (and Download) | ||
| + | |||
| + | ==== Vehicles ==== | ||
| + | * Add New Vehicle | ||
| + | * Rename Vehicle | ||
| + | * Delete Vehicle | ||
| + | * Assign to GPS Device (Association) | ||
| + | * Set Time Range | ||
| + | * Modify Time on Association | ||
| + | * Delete Association | ||
| + | |||
| + | |||
| + | ==== Outside of Tab ==== | ||
| + | * Upload Tracks | ||
access/trackwork_server.1240356384.txt.gz · Last modified: 2012/10/10 17:12 (external edit)
Page Tools
