View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000443 | MMW v4 | DB/FileMonitor | public | 2003-06-02 14:45 | 2007-08-17 01:17 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0000443: CPU utilization is high for an extended period when File Monitor startup scan is enabled | ||||
| Description | This issue originally came up in bug #442. Jiri proposed a solution to allow the function to 'sleep 'x' milliseconds between each track scanned'. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Given that most systems use XP, I wonder if it may be time to eliminate the startup scan, (and possibly have an MM 'agent' running even when MM isn't). |
|
|
I'd prefer to have the startup scan disabled by default. The scanning 'agent' could be implemented too, but with a little lower priority. |
|
|
I wouldn't want to disable the startup scan until we created a scanning agent. i.e. the startup scan is needed if changes were made while MM wasn't running and there was no other process to monitor the changes. |
