mirror of
https://github.com/searxng/searxng.git
synced 2025-07-16 01:39:24 +02:00
d29cf64ce4
In the previous implementation, all databases were loaded into memory when
importing the searx.data package, regardless of whether they were ever needed.
Regardless of this, it is an antipattern to load entire databases into memory
when importing a package or module; databases should be loaded when needed.
Lazy loading is a first step toward improving memory usage and also improves
performance when setting up the runtime environment. Building on this,
subsequent PRs will be able to further optimize memory behavior, e.g., by using
a real database application such as the one already available via
searx.cache.ExpireCache
Related:
- https://github.com/searxng/searxng/discussions/1892
- https://github.com/searxng/searxng/pull/3458
- https://github.com/searxng/searxng/pull/4650
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
|
||
|---|---|---|
| .. | ||
| __init__.py | ||
| ahmia_blacklist.txt | ||
| currencies.json | ||
| engine_descriptions.json | ||
| engine_traits.json | ||
| external_bangs.json | ||
| external_urls.json | ||
| lid.176.ftz | ||
| locales.json | ||
| osm_keys_tags.json | ||
| useragents.json | ||
| wikidata_units.json | ||