mirror
/
Jackett
mirror of https://github.com/Jackett/Jackett
1
0
Fork 0
Code Issues Releases Wiki Activity
Jackett/src/Jackett.Common/Models/TrackerCache.cs

13 lines
318 B
C#
Raw Normal View History

core: redo search cache from scratch. resolves #10382 (#10447) In simple words, when you make a request in Jackett, the results are saved in memory (cache). The next request will return results form the cache improving response time and making fewer requests to the sites. * We assume all indexers/sites are stateless, the same request return the same response. If you change the search term, categories or something in the query Jackett has to make a live request to the indexer. * There are some situations when we don't want to use the cache: ** When we are testing the indexers => if query.IsTest results are not cached ** When the user updates the configuration of one indexer => We call CleanIndexerCache to remove cached results before testing the configuration ** When there is some error/exception in the indexer => The results are not cached so we can retry in the next request * We want to limit the memory usage, so we try to remove elements from cache ASAP: ** Each indexer can have a maximum number of results in memory. If the limit is exceeded we remove old results ** Cached results expire after some time * Users can configure the cache or even disable it
2020-12-11 22:14:21 +00:00
Run dotnet format on solution (#7145)
2020-02-09 02:35:16 +00:00
using System.Collections.Generic;
New: Viewable release cache
2015-07-26 14:22:20 +00:00
Change namespace to Jackett.Common (#2691) Really hope I don't break anything with this Went to have a go at .NET core and it just became too confusing for me with 'Jackett' namespace referring to both Jackett.Common and Jackett
2018-03-10 08:05:56 +00:00
namespace Jackett.Common.Models
New: Viewable release cache
2015-07-26 14:22:20 +00:00
{
core: Apply declarations styles (#7166)
2020-02-10 22:16:19 +00:00
internal class TrackerCache
New: Viewable release cache
2015-07-26 14:22:20 +00:00
{
public string TrackerId { set; get; }
Fix Safari not working not working (Untested). Fix cached download links not proxying the torrent download.
2015-08-05 22:00:09 +00:00
public string TrackerName { set; get; }
core: redo search cache from scratch. resolves #10382 (#10447) In simple words, when you make a request in Jackett, the results are saved in memory (cache). The next request will return results form the cache improving response time and making fewer requests to the sites. * We assume all indexers/sites are stateless, the same request return the same response. If you change the search term, categories or something in the query Jackett has to make a live request to the indexer. * There are some situations when we don't want to use the cache: ** When we are testing the indexers => if query.IsTest results are not cached ** When the user updates the configuration of one indexer => We call CleanIndexerCache to remove cached results before testing the configuration ** When there is some error/exception in the indexer => The results are not cached so we can retry in the next request * We want to limit the memory usage, so we try to remove elements from cache ASAP: ** Each indexer can have a maximum number of results in memory. If the limit is exceeded we remove old results ** Cached results expire after some time * Users can configure the cache or even disable it
2020-12-11 22:14:21 +00:00
public Dictionary<string, TrackerCacheQuery> Queries = new Dictionary<string, TrackerCacheQuery>();
New: Viewable release cache
2015-07-26 14:22:20 +00:00
}
}