Hacker News Reader

I'm curious -- is it the binary size that's a problem, or the resident size in memory? Demand paging should help, although you'd be stuck with carrying the enlarged binary.

View on HN

my gut feeling tell it will be both memory and cpu utilization. cant be sure, until I can find good way to measure it.

ps RSS measurement is pretty good for a start (although note in a forked process, shared copy-on-write pages are both reported as RSS for both the parent and child process).

top reports this as RES.

IIRC, debugging information is in a separate part of the process, so it's not loaded until it's used. Does that make it free? Probably not quite, but the kernel can ignore it until the process (presumably via its debugger) looks at it.

If only there was a monitoring system you could install to measure such a thing.

Reply on news.ycombinator.com