Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A aurweb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch LinuxArch Linux
  • aurweb
  • Repository
Switch branch/tag
  • aurweb
  • web
  • lib
  • aurjson.class.php
Find file BlameHistoryPermalink
  • Lukas Fleischer's avatar
    aurjson: use APCu/memcached for rate limiting · 86e4cd07
    Lukas Fleischer authored Nov 02, 2019
    
    
    There's no need to use permanent storage for rate limiting information;
    try to keep it in memory if caching is enabled.
    
    From experiments with our live setup, this reduces the number of
    INSERT/DELETE operations per second from 15 to almost 0. Disk writes on
    the server hosting the AUR are reduced by 90% (from ~3MB/s to ~300kB/s).
    
    Signed-off-by: Lukas Fleischer's avatarLukas Fleischer <lfleischer@archlinux.org>
    86e4cd07