forked from zaclys/searxng
01e2648e93
The timeouts in settings.yml is about the total time (not only the HTTP request but also the prepare the request and parsing the response) It was more or less the case before since the threaded_requests function ignores the thread after the timeout even the HTTP request is ended. New / changed stats : * page_load_time : record the HTTP request time * page_load_count: the number of HTTP request * engine_time : the execution total time of an engine * engine_time_count : the number of "engine_time" measure The avg response times in the preferences are the engine response time (engine_load_time / engine_load_count) To sum up : * Search.search() filters the engines that can't process the request * Search.search() call search_multiple_requests function * search_multiple_requests creates one thread per engine, each thread runs the search_one_request function * search_one_request calls the request function, make the HTTP request, calls the response function, extends the result_container * search_multiple_requests waits for the the thread to finish (or timeout) |
||
|---|---|---|
| examples | ||
| searx | ||
| tests | ||
| utils | ||
| .coveragerc | ||
| .gitignore | ||
| .landscape.yaml | ||
| .travis.yml | ||
| AUTHORS.rst | ||
| CHANGELOG.rst | ||
| Dockerfile | ||
| LICENSE | ||
| README.rst | ||
| babel.cfg | ||
| manage.sh | ||
| requirements-dev.txt | ||
| requirements.txt | ||
| setup.py | ||
| tox.ini | ||
README.rst
searx
A privacy-respecting, hackable metasearch engine.
List of running instances.
See the documentation and the wiki for more information.
Installation
- clone source:
git clone https://github.com/asciimoo/searx.git && cd searx - install dependencies:
./manage.sh update_packages - edit your settings.yml (set your
secret_key!) - run
python searx/webapp.pyto start the application
For all the details, follow this step by step installation
Bugs
Bugs or suggestions? Visit the issue tracker.