Comment 19 for bug 1704396
Revision history for this message
| Jeff Davis (jdavis-sitka) wrote Re: Slowness for metecord and one-hit searches in 2.12 | #19 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Another example of a failed search (no hits) which succeeds on a second attempt (multiple hits), this time with Postgres query durations:
http://
If I'm reading our logs correctly, the db query takes a reasonable amount of time: 140ms for the failed search vs. 168ms for the successful followup. So I don't think the query itself is the issue.
As before, the failed search gives us a series of OpenSRF log messages, then the "flushing data from socket..." message about 1 second later, then one final log entry for that trace 60-70 seconds after that.