GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Implement caching system · Issue #80 · Ktt-Development/simplehttpserver

This repository was archived by the owner on Jul 31, 2022. It is now read-only.
This repository was archived by the owner on Jul 31, 2022. It is now read-only.

Implement caching system #80

Copy link
Copy link
Closed
#107
Closed
Implement caching system#80
#107
Copy link
Assignees
Katsute
Labels
feature requestRequest a featureRequest a featureoptimizationOptimizationsOptimizations
Milestone
4.0.0

Description

@Katsute
Katsute
opened on Jul 31, 2020
Issue body actions

Prerequisites

If all checks are not passed then the request will be closed

  • I have checked that no other similar feature request already exists
  • The feature request makes sense for the project

Proposal

Describe the feature that should be added

Implement caching for liveload

https://crunchify.com/how-to-create-a-simple-in-memory-cache-in-java-lightweight-cache/

Reasoning

Explain why this feature should be added

Efficiency and memory.

Activity

  1. Katsute
    added
    feature requestRequest a featureRequest a feature
    on Jul 31, 2020
  2. Katsute
    self-assigned this
    on Jul 31, 2020
  3. Katsute commented on Sep 19, 2020

    @Katsute
    Katsute
    on Sep 19, 2020
    MemberAuthor
    More actions

    When a file is first accessed:

    • create a long with the expiry
    • set the timer to a lower number if its lower than current

    When the timer reached end:

    • remove any files that passed expiry
    • if lowest expiry passed reset to next lowest timer

    If a file is reaccesed:

    • reset expiry for that file
  4. Katsute
    added
    optimizationOptimizationsOptimizations
    on Sep 19, 2020
  5. Katsute
    added this to the 4.0.0 milestone on Oct 13, 2020
  6. Katsute commented on Oct 17, 2020

    @Katsute
    Katsute
    on Oct 17, 2020
    MemberAuthor
    More actions

    Update file cache when the last modified time changes.

  7. Katsute commented on Oct 17, 2020

    @Katsute
    Katsute
    on Oct 17, 2020
    MemberAuthor
    More actions

    A cache byte loading option could require a file cache adapter (and throw illegal args otherwise).

    Parameter can be long millis or double and TimeUnit.

  8. Katsute commented on Oct 18, 2020

    @Katsute
    Katsute
    on Oct 18, 2020
    MemberAuthor
    More actions

    Instead of a timer instead only clear cache on an exchange.
    Have a long for the closest file expiry and then iterate through each file to clear bytes.

    After read set expiry to -1 then use that to determine if to read file when accessed again.

  9. Katsute commented on Oct 19, 2020

    @Katsute
    Katsute
    on Oct 19, 2020
    MemberAuthor
    More actions

    A timer will not be used because this would introduce some thread instability with multiple threads.

  10. Katsute
    added a commit that references this issue on Oct 19, 2020

    Implement cache #80

    a26d1bf
  11. Katsute
    closed this as completedin #107on Oct 20, 2020
  12. Katsute
    added a commit that references this issue on Oct 20, 2020

    Optimize MODLOAD (removed WATCHLOAD) and Add CACHELOAD. (#107)

    be8d868
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @Katsute
    Katsute

Labels

feature requestRequest a featureRequest a featureoptimizationOptimizationsOptimizations

Type

No type

Projects

No projects

    Milestone

    • 4.0.0

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.