TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

How devs should respond: Memory allocation for very large element sizes

14 点作者 redshirt大约 7 年前

1 comment

redshirt大约 7 年前
Found this after reading the tastes paper on front page. It’s the most fabulously long and complete GitHub issues post I’ve ever seen, almost a blog post in and of itself. I can definitely appreciate the details in the allocation process the authors of RaftLib have implemented after reading this. I’ve never seen garbage collection implemented in a dataflow framework before..actually, haven’t seen that many actual dataflow/channels implementations for C++...they typically die out quickly. Definitely going to check this out more.