Skip to content

Inaccurate starting memory usage #10

@kyfuse

Description

@kyfuse

Describe the bug
Microsoft Azure seems to do some sort of throttling on VMs that have been inactive for a while. So, JudgeLite reports an incorrect memory used value (~30 mb too high) for the first submission after a period of inactivity.

To Reproduce

  1. Go to HHS Programing Club's website
  2. Submit something and look at the memory usage
  3. Submit again and look at the lower memory usage.

Expected behavior
The memory used value should be accurate.

Additional context
This is probably Azure's fault. However, it could be countered by running a 'dummy' submission before the actual one after a period of inactivity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions