| Summary: | Error report web: Optimize searching times | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Yocto Project Subprojects] Error Reporting tool | Reporter: | Aníbal Limón <anibal.limon> | ||||
| Component: | Error Reporting Tool | Assignee: | Tim Orling <tim.orling> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | Medium | CC: | belen.barros.pena, benjamin.esquivel, changqing.li, juan.m.cruz.alcaraz, randy.macleod, richard.purdie, tim.orling | ||||
| Version: | unspecified | ||||||
| Target Milestone: | Future | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
|
Description
Aníbal Limón
2016-05-17 22:22:13 UTC
We did tweak some things like the link used from the autobuilder so its no longer a full text search but just searching for specific revisions. Does that help your usecase or not? We're struggling to figure out the priority of this without knowing what usecases its impacting. If there is a significant impact we could make it a Medium+. We could also assign to someone on the GDC team, depending on how Michael and GDC want to handle this. (In reply to comment #1) > We did tweak some things like the link used from the autobuilder so its no > longer a full text search but just searching for specific revisions. Does > that help your usecase or not? We're struggling to figure out the priority > of this without knowing what usecases its impacting. If there is a > significant impact we could make it a Medium+. We could also assign to > someone on the GDC team, depending on how Michael and GDC want to handle > this. We can workaround the search over log using only the link from auto builder for access the failures also using specific revisions but this not solve the current searching problem if the search functionality isn't needed may be is better to remove it instead of leave as is and only using specific revisions and AB link. Created attachment 3182 [details]
mysql slow query log
When did a search of smart, in the current db.
(In reply to comment #3) > Created attachment 3182 [details] > mysql slow query log > > When did a search of smart, in the current db. As summary the query took 440s, # Query_time: 440.112315 Lock_time: 0.000082 Rows_sent: 1 Rows_examined: 79488 Fine to take this bug, pretty easy to implement. Note that we already have a bug #6541 to improve the search on the UI side which may help where people haven't discovered out how to do the correct query. We would need to special case when the backend database selection is mysql and create a full text index on the log field. We would also need to check which backend database is in use to be able to switch between the querying method. https://docs.djangoproject.com/en/1.8/ref/models/querysets/#search Still slow... Still valid. |