memory_usage
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | memory_usage [2008/07/28 05:14] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ======The client uses too much memory===== | ||
+ | If you think the client is using too much memory, you may think there is a | ||
+ | memory leak. But before you report a bug, consider the following common | ||
+ | causes of high memory usage, and ways to reduce usage. | ||
+ | |||
+ | * A window that is in scrollback mode does not trim its scrollback -- it will grow without any limit. | ||
+ | * A window that has an extremely large scrollback (10,000 lines). | ||
+ | * A window that has an extremely large lastlog (5,000 lines). | ||
+ | * A lot of windows are open. Even if the lastlog and scrollback sizes are modest, if you have a lot of windows open (over 20), it can add up fast. | ||
+ | * A lot of aliases and assigns. | ||
+ | * A lot of channels. | ||
+ | * A lot of servers. | ||
+ | |||
+ | Unfortunately, | ||
+ | of memory reported in ' | ||
+ | memory that is free()d is saved for re-use and is not returned to the | ||
+ | operating system. | ||
+ | is smart, and memory that is allocated but unused will be paged out. | ||
+ | |||
memory_usage.txt · Last modified: 2008/07/28 05:14 by 127.0.0.1