Closed Bug 773721 Opened 13 years ago Closed 13 years ago

Make sure pancake-search uses the Curl http client

Categories

(Pancake Graveyard :: Back-end, defect)

Product:
Pancake Graveyard
Component:
Back-end
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: st3fan, Assigned: st3fan)

Details

This should speed up HTTPS requests to Bing.
https://bitbucket.org/mozillapancake/pancake/changeset/6dba9c64d7a7 - Configure AsyncHTTPClient https://bitbucket.org/mozillapancake/pancake/changeset/a43bb04d2449 - Proper fix for above :-/ https://bitbucket.org/mozillapancake/pancake/changeset/5f6054d5dbda - RPM to include dependency on pycurl Only the RPM has the PyCURL dependency. It is not in setup.py because pycurl it fails to build/install on OS X 10.7
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Before: [I 120713 17:51:15 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 814.72ms [I 120713 17:51:18 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 557.77ms [I 120713 17:51:19 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 609.41ms [I 120713 17:51:21 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 493.44ms [I 120713 17:51:23 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 419.01ms [I 120713 17:51:25 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 519.92ms [I 120713 17:51:27 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 496.50ms After: [I 120713 17:54:27 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 292.27ms [I 120713 17:54:29 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 307.05ms [I 120713 17:54:43 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 317.44ms [I 120713 17:54:45 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 391.20ms [I 120713 17:54:46 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 327.72ms [I 120713 17:54:49 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 349.56ms [I 120713 17:54:51 web:1393] 200 GET /search/bing?q=cheese (127.0.0.1) 277.70ms
You need to log in before you can comment on or make changes to this bug.