Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
caravaggio
caravaggio
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 2
    • Merge requests 2
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Fabrizio Ruggeri
  • caravaggiocaravaggio
  • Issues
  • #25

Closed
Open
Created Sep 19, 2018 by Fabrizio Ruggeri@ramielMaintainer

Faster caches

save method in cache is called before sending the response to the client. If the operation done by the cache is not mandatory to have a correct result, it should not be waited.

e.g.

The file cache awaits for the buffer to be created on disk before returning. It should return immediately and silently (just logged) fail. Same thing for the memory cache.
This cannot be done for the S3 cache where we need to know the file path.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking