TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Optimising Garbage Collection Overhead in Sigma

33 pointsby psibialmost 10 years ago

2 comments

ezyangalmost 10 years ago
I mentored Giovanni on the two-step allocator patch, and in the process we discovered that on Windows, page tables for all of your reserved address space are counted towards the memory limits of your process. This also affects Go (<a href="https:&#x2F;&#x2F;golang.org&#x2F;issue&#x2F;5402" rel="nofollow">https:&#x2F;&#x2F;golang.org&#x2F;issue&#x2F;5402</a> and <a href="https:&#x2F;&#x2F;golang.org&#x2F;issue&#x2F;5236" rel="nofollow">https:&#x2F;&#x2F;golang.org&#x2F;issue&#x2F;5236</a>) which uses a similar trick of reserving virtual address space for its heap. If anyone has ideas for how to deal with this on Windows I think many people would be quite interested :)
ameliusalmost 10 years ago
&gt; Sigma, which is part of the anti-spam infrastructure<p>Sounds like something which can be done as a batch-job with little memory. Or not?
评论 #9964052 未加载
评论 #9964063 未加载