View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007992 | MMW v4 | DB/FileMonitor | public | 2011-06-22 18:14 | 2011-09-08 00:37 |
| Reporter | jiri | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Platform | Windows | OS | 7 | OS Version | - |
| Product Version | 4.0 | ||||
| Target Version | 4.0 | Fixed in Version | 4.0 | ||
| Summary | 0007992: ANALYZE DB after major changes | ||||
| Description | While testing 0007985 I found out that having the DB ANALYZEd is sometimes very important in order to get fast results. For example, expanding a Location node on a large unanalyzed DB took ~20sec, while after analyzation it's pretty much immediate. I think that we could do few things in order to make this working smoothly for users: 1. Document somewhere, that any performance problems should be fixed by running DB Maintenance (Quick is enough), which does that ANALYZE command. 2. Execute ANALYZE on DB update to 4.0. 3. Execute ANALYZE after any DB scan that added (really added, not only re-scanned) let's say >1000 tracks (or maybe better >10-30% of already existing tracks in DB?). | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1395 | ||||
