当前位置:首页 > 文章列表 > Golang > Go问答 > memstat HeapInuse 和 TotalAlloc 需要解释

memstat HeapInuse 和 TotalAlloc 需要解释

来源:stackoverflow 2024-04-04 20:00:37 0浏览 收藏

本篇文章向大家介绍《memstat HeapInuse 和 TotalAlloc 需要解释》,主要包括,具有一定的参考价值,需要的朋友可以参考一下。

问题内容

我想要转储 golang memstat

package main

import (
    "fmt"
    "github.com/dustin/go-humanize"
    "runtime"
    "time"
)

func main() {
    for {
        var mem = new(runtime.memstats)
        runtime.readmemstats(mem)
        fmt.println("heapinuse:", humanize.bytes(mem.heapinuse), "totalalloc:", humanize.bytes(mem.totalalloc))

        allocate()
        time.sleep(100 * time.millisecond)
    }

}

func allocate() {
    //  0.25mb
    _ = make([]byte, int((1<<20)*0.25))
}

当我转储内存信息时

HeapInuse: 418 kB TotalAlloc: 154 kB ? why  HeapInuse bigger than TotalAlloc
HeapInuse: 688 kB TotalAlloc: 417 kB
HeapInuse: 950 kB TotalAlloc: 680 kB
HeapInuse: 1.2 MB TotalAlloc: 942 kB
HeapInuse: 1.5 MB TotalAlloc: 1.2 MB
HeapInuse: 1.8 MB TotalAlloc: 1.5 MB
HeapInuse: 2.0 MB TotalAlloc: 1.7 MB
HeapInuse: 2.3 MB TotalAlloc: 2.0 MB
HeapInuse: 2.5 MB TotalAlloc: 2.3 MB
HeapInuse: 2.8 MB TotalAlloc: 2.5 MB
HeapInuse: 3.1 MB TotalAlloc: 2.8 MB
HeapInuse: 3.3 MB TotalAlloc: 3.0 MB
HeapInuse: 3.6 MB TotalAlloc: 3.3 MB
HeapInuse: 3.9 MB TotalAlloc: 3.6 MB
HeapInuse: 4.1 MB TotalAlloc: 3.8 MB
HeapInuse: 4.4 MB TotalAlloc: 4.1 MB
HeapInuse: 410 kB TotalAlloc: 4.4 MB

我发现 heapinuse 比 totalalloc 大?但我不明白原因?我认为totalalloc应该包括heapinuse。


正确答案


我们来看看下面的官方评论:

总分配

// totalalloc is cumulative bytes allocated for heap objects.
//
// totalalloc increases as heap objects are allocated, but
// unlike alloc and heapalloc, it does not decrease when
// objects are freed.
totalalloc uint64

heapinuse

// heapinuse is bytes in in-use spans.
//
// in-use spans have at least one object in them. these spans
// can only be used for other objects of roughly the same
// size.
//
// heapinuse minus heapalloc estimates the amount of memory
// that has been dedicated to particular size classes, but is
// not currently being used. this is an upper bound on
// fragmentation, but in general this memory can be reused
// efficiently.
heapinuse uint64
  • heapinuse 是(从操作系统)分配的内存,不能被对象使用
  • totalalloc是为堆对象分配的内存

让我们尝试一下heapalloc

// heapalloc is bytes of allocated heap objects.
//
// "allocated" heap objects include all reachable objects, as
// well as unreachable objects that the garbage collector has
// not yet freed. specifically, heapalloc increases as heap
// objects are allocated and decreases as the heap is swept
// and unreachable objects are freed. sweeping occurs
// incrementally between gc cycles, so these two processes
// occur simultaneously, and as a result heapalloc tends to
// change smoothly (in contrast with the sawtooth that is
// typical of stop-the-world garbage collectors).
heapalloc uint64

结果

HeapAlloc: 148 kB HeapInuse: 401 kB TotalAlloc: 148 kB
HeapAlloc: 412 kB HeapInuse: 664 kB TotalAlloc: 412 kB
HeapAlloc: 675 kB HeapInuse: 926 kB TotalAlloc: 675 kB
HeapAlloc: 937 kB HeapInuse: 1.2 MB TotalAlloc: 937 kB
HeapAlloc: 1.2 MB HeapInuse: 1.5 MB TotalAlloc: 1.2 MB
HeapAlloc: 1.5 MB HeapInuse: 1.7 MB TotalAlloc: 1.5 MB
HeapAlloc: 1.7 MB HeapInuse: 2.0 MB TotalAlloc: 1.7 MB
HeapAlloc: 2.0 MB HeapInuse: 2.2 MB TotalAlloc: 2.0 MB
HeapAlloc: 2.2 MB HeapInuse: 2.5 MB TotalAlloc: 2.2 MB
HeapAlloc: 2.5 MB HeapInuse: 2.8 MB TotalAlloc: 2.5 MB
HeapAlloc: 2.8 MB HeapInuse: 3.0 MB TotalAlloc: 2.8 MB
HeapAlloc: 3.0 MB HeapInuse: 3.3 MB TotalAlloc: 3.0 MB
HeapAlloc: 3.3 MB HeapInuse: 3.6 MB TotalAlloc: 3.3 MB
HeapAlloc: 3.6 MB HeapInuse: 3.8 MB TotalAlloc: 3.6 MB
HeapAlloc: 3.8 MB HeapInuse: 4.1 MB TotalAlloc: 3.8 MB
HeapAlloc: 4.1 MB HeapInuse: 4.3 MB TotalAlloc: 4.1 MB
HeapAlloc: 134 kB HeapInuse: 393 kB TotalAlloc: 4.4 MB
HeapAlloc: 398 kB HeapInuse: 664 kB TotalAlloc: 4.6 MB
HeapAlloc: 660 kB HeapInuse: 926 kB TotalAlloc: 4.9 MB
HeapAlloc: 923 kB HeapInuse: 1.2 MB TotalAlloc: 5.1 MB
HeapAlloc: 1.2 MB HeapInuse: 1.4 MB TotalAlloc: 5.4 MB
HeapAlloc: 1.4 MB HeapInuse: 1.7 MB TotalAlloc: 5.7 MB
HeapAlloc: 1.7 MB HeapInuse: 2.0 MB TotalAlloc: 5.9 MB
HeapAlloc: 2.0 MB HeapInuse: 2.2 MB TotalAlloc: 6.2 MB
HeapAlloc: 2.2 MB HeapInuse: 2.5 MB TotalAlloc: 6.5 MB
HeapAlloc: 2.5 MB HeapInuse: 2.8 MB TotalAlloc: 6.7 MB
HeapAlloc: 2.8 MB HeapInuse: 3.0 MB TotalAlloc: 7.0 MB
HeapAlloc: 3.0 MB HeapInuse: 3.3 MB TotalAlloc: 7.2 MB
HeapAlloc: 3.3 MB HeapInuse: 3.5 MB TotalAlloc: 7.5 MB
HeapAlloc: 3.5 MB HeapInuse: 3.8 MB TotalAlloc: 7.8 MB
HeapAlloc: 3.8 MB HeapInuse: 4.1 MB TotalAlloc: 8.0 MB
HeapAlloc: 4.1 MB HeapInuse: 4.3 MB TotalAlloc: 8.3 MB
HeapAlloc: 136 kB HeapInuse: 401 kB TotalAlloc: 8.6 MB
HeapAlloc: 400 kB HeapInuse: 664 kB TotalAlloc: 8.8 MB
HeapAlloc: 662 kB HeapInuse: 926 kB TotalAlloc: 9.1 MB
HeapAlloc: 924 kB HeapInuse: 1.2 MB TotalAlloc: 9.3 MB
HeapAlloc: 1.2 MB HeapInuse: 1.4 MB TotalAlloc: 9.6 MB
HeapAlloc: 1.4 MB HeapInuse: 1.7 MB TotalAlloc: 9.9 MB
HeapAlloc: 1.7 MB HeapInuse: 2.0 MB TotalAlloc: 10 MB
HeapAlloc: 2.0 MB HeapInuse: 2.2 MB TotalAlloc: 10 MB
HeapAlloc: 2.2 MB HeapInuse: 2.5 MB TotalAlloc: 11 MB
HeapAlloc: 2.5 MB HeapInuse: 2.8 MB TotalAlloc: 11 MB
HeapAlloc: 2.8 MB HeapInuse: 3.0 MB TotalAlloc: 11 MB
HeapAlloc: 3.0 MB HeapInuse: 3.3 MB TotalAlloc: 11 MB
HeapAlloc: 3.3 MB HeapInuse: 3.5 MB TotalAlloc: 12 MB
HeapAlloc: 3.5 MB HeapInuse: 3.8 MB TotalAlloc: 12 MB
HeapAlloc: 3.8 MB HeapInuse: 4.1 MB TotalAlloc: 12 MB
HeapAlloc: 4.1 MB HeapInuse: 4.3 MB TotalAlloc: 12 MB
HeapAlloc: 136 kB HeapInuse: 401 kB TotalAlloc: 13 MB
HeapAlloc: 400 kB HeapInuse: 664 kB TotalAlloc: 13 MB
HeapAlloc: 663 kB HeapInuse: 926 kB TotalAlloc: 13 MB
HeapAlloc: 925 kB HeapInuse: 1.2 MB TotalAlloc: 14 MB
HeapAlloc: 1.2 MB HeapInuse: 1.4 MB TotalAlloc: 14 MB
HeapAlloc: 1.4 MB HeapInuse: 1.7 MB TotalAlloc: 14 MB

今天关于《memstat HeapInuse 和 TotalAlloc 需要解释》的内容就介绍到这里了,是不是学起来一目了然!想要了解更多关于的内容请关注golang学习网公众号!

版本声明
本文转载于:stackoverflow 如有侵犯,请联系study_golang@163.com删除
API 网关 -> Go Lambda 参数API 网关 -> Go Lambda 参数
上一篇
API 网关 -> Go Lambda 参数
无法从连接读取:远程错误:tls:未知证书
下一篇
无法从连接读取:远程错误:tls:未知证书
查看更多
最新文章
查看更多
课程推荐
  • 前端进阶之JavaScript设计模式
    前端进阶之JavaScript设计模式
    设计模式是开发人员在软件开发过程中面临一般问题时的解决方案,代表了最佳的实践。本课程的主打内容包括JS常见设计模式以及具体应用场景,打造一站式知识长龙服务,适合有JS基础的同学学习。
    543次学习
  • GO语言核心编程课程
    GO语言核心编程课程
    本课程采用真实案例,全面具体可落地,从理论到实践,一步一步将GO核心编程技术、编程思想、底层实现融会贯通,使学习者贴近时代脉搏,做IT互联网时代的弄潮儿。
    514次学习
  • 简单聊聊mysql8与网络通信
    简单聊聊mysql8与网络通信
    如有问题加微信:Le-studyg;在课程中,我们将首先介绍MySQL8的新特性,包括性能优化、安全增强、新数据类型等,帮助学生快速熟悉MySQL8的最新功能。接着,我们将深入解析MySQL的网络通信机制,包括协议、连接管理、数据传输等,让
    499次学习
  • JavaScript正则表达式基础与实战
    JavaScript正则表达式基础与实战
    在任何一门编程语言中,正则表达式,都是一项重要的知识,它提供了高效的字符串匹配与捕获机制,可以极大的简化程序设计。
    487次学习
  • 从零制作响应式网站—Grid布局
    从零制作响应式网站—Grid布局
    本系列教程将展示从零制作一个假想的网络科技公司官网,分为导航,轮播,关于我们,成功案例,服务流程,团队介绍,数据部分,公司动态,底部信息等内容区块。网站整体采用CSSGrid布局,支持响应式,有流畅过渡和展现动画。
    484次学习
查看更多
AI推荐
  • SEO  AI Mermaid 流程图:自然语言生成,文本驱动可视化创作
    AI Mermaid流程图
    SEO AI Mermaid 流程图工具:基于 Mermaid 语法,AI 辅助,自然语言生成流程图,提升可视化创作效率,适用于开发者、产品经理、教育工作者。
    702次使用
  • 搜获客笔记生成器:小红书医美爆款内容AI创作神器
    搜获客【笔记生成器】
    搜获客笔记生成器,国内首个聚焦小红书医美垂类的AI文案工具。1500万爆款文案库,行业专属算法,助您高效创作合规、引流的医美笔记,提升运营效率,引爆小红书流量!
    713次使用
  • iTerms:一站式法律AI工作台,智能合同审查起草与法律问答专家
    iTerms
    iTerms是一款专业的一站式法律AI工作台,提供AI合同审查、AI合同起草及AI法律问答服务。通过智能问答、深度思考与联网检索,助您高效检索法律法规与司法判例,告别传统模板,实现合同一键起草与在线编辑,大幅提升法律事务处理效率。
    735次使用
  • TokenPony:AI大模型API聚合平台,一站式接入,高效稳定高性价比
    TokenPony
    TokenPony是讯盟科技旗下的AI大模型聚合API平台。通过统一接口接入DeepSeek、Kimi、Qwen等主流模型,支持1024K超长上下文,实现零配置、免部署、极速响应与高性价比的AI应用开发,助力专业用户轻松构建智能服务。
    799次使用
  • 迅捷AIPPT:AI智能PPT生成器,高效制作专业演示文稿
    迅捷AIPPT
    迅捷AIPPT是一款高效AI智能PPT生成软件,一键智能生成精美演示文稿。内置海量专业模板、多样风格,支持自定义大纲,助您轻松制作高质量PPT,大幅节省时间。
    690次使用
微信登录更方便
  • 密码登录
  • 注册账号
登录即同意 用户协议隐私政策
返回登录
  • 重置密码