Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A arachni
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 125
    • Issues 125
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arachni - Web Application Security Scanner Framework
  • arachni
  • Issues
  • #698
Closed
Open
Issue created Apr 14, 2016 by Administrator@rootContributor

Support::Cache should offload to disk

Created by: Zapotek

Update the Support::Cache classes to offload pruned entries to disk, rather than removing them completely.

  • Use one file per instance.
    • Keep the file-descriptor open.
    • Delete via a finalizer
  • Serialize using MessagePack.
  • Keep track of entry positions by offsets and sizes.
    • To be used for #seeking and #reading.

This should have a massive impact on RAM consumption, CPU utilization and overall performance as less entries will be stored in memory but a lot more will cached.

Assignee
Assign to
Time tracking