Project

Profile

Help

Actions
Send by e-mail Copy link

Task #8804

closed

[EPIC] Use Redis to add caching abilities to Pulp

Added by gerrod almost 3 years ago. Updated over 2 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

100%

Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Performance
Sprint:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulpcore/2002":https://github.com/pulp/pulpcore/issues/2002

Redis is already used by Pulp for its tasking system and can also be used to create a cache for Pulp. The cache would be used to store the responses for API and content requests to reduce the amount of database requests Pulp has to serve. The cache should be optionable and have easily tunable parameters for the user.

Sub-issues 3 (0 open — 3 closed)

Task #8805: Cache the responses of the content appCLOSED - CURRENTRELEASEgerrod

Actions
Task #8806: Allow plugin writers to cache the responses of their APIsCLOSED - DUPLICATElmjachky

Actions
Issue #8998: Ensure that Redis being down or unavailable does not interrupt workflows using the cacheCLOSED - DUPLICATEActions

Related issues

Related to Pulp - Issue #8180: Content serving performance tuningCLOSED - DUPLICATEActions
Actions
Copy link
 #1

Updated by gerrod almost 3 years ago

  • Related to Issue #8180: Content serving performance tuning added
Actions
Copy link
 #2

Updated by pulpbot over 2 years ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE
Actions
Send by e-mail Copy link

Also available in: Atom PDF