-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
todo #154
Comments
Designing A Fast Concurrent Hash Table |
https://15721.courses.cs.cmu.edu/spring2019/papers/17-hashjoins/richter-vldb2015.pdf A Seven-Dimensional Analysis of Hashing Methods and its |
Hyrum's Law in Golang https://abenezer.org/blog/hyrum-law-in-golang 任何接口一单定下来就会被依赖上。ABI stable |
https://tokio.rs/blog/2019-10-scheduler inko/issues/337 |
bhumikamittal7/graphstore_doc |
Memento_Filter |
mgtv-tech/redis-GunYu |
NUMA 背景 CPU概念 Socket(芯片插槽) > NUMA node(一个插槽可能有一个或多个NUMA node) > CPU core (一个NUMA node下有多个CPU core) > thread (一个CPU core可以有一个或两个thread(超线程)) 前端总线共享 内存存在距离 所以就有了所谓的跨NUMA 节点 分配内存的问题 检查清单 NUMA node(s): 2 如果只有一个就不用看了 numactl -H 更详细一些 numastat 重点关注numa miss和numa_foreign 分别代表缓存失效和跨节点访问内存 可以简单计算cache miss rate 2% 影响有限 numactl --hardware 查看核心以及对应的cpu 是否均衡? sysctl -w kernel.numa_balancing=0 规避网卡绑核 ethtool -i eth0 https://tidb.net/book/tidb-monthly/2022/2022-04/usercase/NUMA-node 网卡影响案例一例 https://tech.meituan.com/2018/11/15/docker-architecture-and-evolution-practice.html 选择绑定策略 numactl --show,常见策略内存分配: strict/default: interleave: numactl --interleave=all 场景 最小化跨节点的内存访问,提高缓存命中率和内存访问性能 preferred: preferred相比membind不会失败,可以和membind组合,实现既要有要 physcpubind 最小化上下文切换场景 需要确认是CPU cache影响还是NUMA 跨内存影响来选择cpunodebind还是这个 组合使用 numactl --cpunodebind=0 --preferred=0 优先0内存 numactl --cpunodebind=0 --membind=0 --preferred=0 --physcpubind=0,1,2,3 存在上层宿主机numa配置影响容器案例 https://cloud.tencent.com/developer/article/1543313 宿主机配了,但容器没配 宿主机没配,容器可以配,也能生效 taskset -pc $$ #pid 可以查看容器使用的CPU亲和情况 上层可以通过k8s kubelet 或者docker自身也可以配置 k8s numa.zone-topology |
percpu_arena:percpu 和numactl冲突 |
MALLOC_CONF="background_thread:true,dirty_decay_ms:4000,thp:always,metadata_thp:always" |
facebook /rocksdb/pull/12540/files#diff-85aa8bd0327318a639a4c8e84b7890713f09e675017b6e9c06f044c2b0dc512a 另一种思路,跟踪mannifest变动同步文件 |
blobdb问题 facebook /rocksdb/issues/11570 批量写gc策略错误 10657 问题相同 |
stas00/ml-engineering intel/ScalableVectorSearch |
No description provided.
The text was updated successfully, but these errors were encountered: