14.11.2011, 22:32
TinyWall has been written for .Net and the memory requirements for .Net should not be judged by the task manager. Most "used" RAM is Microsoft stuff and is reused for all .Net applications. So if you see .Net processes each using a lot of megabytes, a lot of that is shared and is double counted by the task manager!
In the specific case of TinyWall, I have already performed memory usage analysis because someone was also asking about the memory usage per e-mail. The actual heap memory that TinyWall uses is about 1.4Megs, a further 13Megs are process specific .Net overhead and over-reserved heap. Again, this is much better than it looks as this is unused heap space and .Net is able to give it back to other applications if needed. All the rest, which were 22Megs on my computer, are .Net stuff shared between other processes too, so that really does not count towards memory usage.
In the specific case of TinyWall, I have already performed memory usage analysis because someone was also asking about the memory usage per e-mail. The actual heap memory that TinyWall uses is about 1.4Megs, a further 13Megs are process specific .Net overhead and over-reserved heap. Again, this is much better than it looks as this is unused heap space and .Net is able to give it back to other applications if needed. All the rest, which were 22Megs on my computer, are .Net stuff shared between other processes too, so that really does not count towards memory usage.