File: system_resource_util_test.c

package info (click to toggle)
aws-crt-python 0.20.4%2Bdfsg-1~bpo12%2B1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm-backports
  • size: 72,656 kB
  • sloc: ansic: 381,805; python: 23,008; makefile: 6,251; sh: 4,536; cpp: 699; ruby: 208; java: 77; perl: 73; javascript: 46; xml: 11
file content (37 lines) | stat: -rw-r--r-- 1,172 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
/**
 * Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
 * SPDX-License-Identifier: Apache-2.0.
 */

#include <aws/common/byte_buf.h>
#include <aws/common/device_random.h>
#include <aws/common/system_resource_util.h>

#include <aws/testing/aws_test_harness.h>

static int s_test_memory_usage_maxrss(struct aws_allocator *allocator, void *ctx) {
    (void)ctx;

    /*
     * Note: mem usage apis currently rely on getrusage on posix systems.
     * On freebsd maxrss seems to return current process rss based on testing,
     * while on every other posix platform maxrss is high water mark for rss
     * over the program lifetime.
     * Workaround it by allocating a buffer first. Long term using procfs should
     * avoid the issue.
     */
    struct aws_byte_buf temp;
    aws_byte_buf_init(&temp, allocator, 8 * 1024 * 1024);
    ASSERT_SUCCESS(aws_device_random_buffer(&temp));

    struct aws_memory_usage_stats mu;
    ASSERT_SUCCESS(aws_init_memory_usage_for_current_process(&mu));

    ASSERT_TRUE(mu.maxrss > 0);

    aws_byte_buf_clean_up_secure(&temp);

    return 0;
}

AWS_TEST_CASE(test_memory_usage_maxrss, s_test_memory_usage_maxrss)