JJ’s VPS Memory Manager FAQ

FAQ Page Coming Soon

  • jonah
    #1 written by jonah  1 year ago

    i love your jj memory app.

    i used it for 2 weeks, it indeed helps me improve the cost, but it also bring the vps died some time.

    so i’d like to as what’s the parameters mean.

    min memory:
    max memory:
    safety percentage:

    i can know min memory well. but i dont know what’s mean max, eventhough i set up max memory as 1600, sometimes, it still died.
    also what’s the safety percentage means, and how it works.

  • JuanJose
    #2 written by JuanJose  1 year ago

    The first two are explained in the readme:

    MIN_MEMORY should be the minimum memory your VPS uses. 300 is default only because that is the lowest amount of memory you are allowed to use, change this to something more realistic.

    MAX_MEMORY should be a maximum amount of memory you are willing to pay for, remember that the memory manager will only resize to this level if the memory is actually needed. You are not likely to be at this level of memory usage for long periods of time, if you are go buy a dedicated instead.

    as for the last one:

    SAFETY_PERCENTAGE is basically the percentage of total memory that you want to try and keep as a buffer. So if you have 1GB of memory assigned to the VPS and have safety percentage at 20 then the application will try and keep 20% of your memory free.

  • milen
    #3 written by milen  1 year ago

    Hello,
    I was wandering about the button Install/remove Cron above the graph screen. Is is necessary to be “installed” for the Memory Manager to work. Or if not, what is it used for?

  • Mike
    #4 written by Mike 10 months ago

    Why does it take so long for memory resize requests to go through? Thanks!

    [Jul 18 03:00:19] info: Change is requested. Current Memory: 621 Used: 589 Suggestion: 689
    [Jul 18 03:00:19] info: Wrote to process log!
    [Jul 18 03:00:19] info: Current status of resize request: ‘waiting’
    [Jul 18 03:00:26] info: Current status of resize request: ‘waiting’
    [Jul 18 03:00:31] info: Current status of resize request: ‘waiting’
    [Jul 18 03:00:36] info: Current status of resize request: ‘waiting’
    [Jul 18 03:00:41] info: Current status of resize request: ‘running’
    [Jul 18 03:00:46] info: Current status of resize request: ‘running’
    [Jul 18 03:00:51] info: Current status of resize request: ‘running’
    [Jul 18 03:00:56] info: Current status of resize request: ‘running’
    [Jul 18 03:01:01] info: Current status of resize request: ‘running’
    [Jul 18 03:01:06] info: Current status of resize request: ‘running’
    [Jul 18 03:01:11] info: Current status of resize request: ‘running’
    [Jul 18 03:01:16] info: Current status of resize request: ‘running’
    [Jul 18 03:01:21] info: Current status of resize request: ‘running’
    [Jul 18 03:01:26] info: Current status of resize request: ‘running’
    [Jul 18 03:01:31] info: Current status of resize request: ‘running’
    [Jul 18 03:01:36] info: Current status of resize request: ‘running’
    [Jul 18 03:01:41] info: Current status of resize request: ‘running’
    [Jul 18 03:01:46] info: Current status of resize request: ‘running’
    [Jul 18 03:01:46] info: Wrote to graph database: 1342605706000|689|155|0.19|0.20|0.12
    [Jul 18 03:01:51] info: Current status of resize request: ‘running’
    [Jul 18 03:01:56] info: Current status of resize request: ‘running’
    [Jul 18 03:02:01] info: Current status of resize request: ‘running’
    [Jul 18 03:02:06] info: Current status of resize request: ‘running’
    [Jul 18 03:02:12] info: Current status of resize request: ‘running’
    [Jul 18 03:02:17] info: Current status of resize request: ‘running’
    [Jul 18 03:02:22] info: Current status of resize request: ‘running’
    [Jul 18 03:02:27] info: Current status of resize request: ‘running’
    [Jul 18 03:02:32] info: Current status of resize request: ‘success’
    [Jul 18 03:02:42] info: Wrote to graph database: 1342605762000|689|162|0.13|0.18|0.12

  • JuanJose
    #5 written by JuanJose 10 months ago

    That delay comes from the DH end. The waiting, running, and finished status’ are all returned from the API.

  • Comment Feed for this Post
Go to Top