
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-31-2007 04:21 PM
First of all, I'd like to say I love the setup with LanSweeper.
It has been brilliantly fire-and-forget once I got it configured correctly. But I have been watching my server and the service seems to steadily increase in RAM utilization with each client. Is there a built-in memory purge, or is there a preferred method to keep this from hitting a gig of used memory?
Thanks!
It has been brilliantly fire-and-forget once I got it configured correctly. But I have been watching my server and the service seems to steadily increase in RAM utilization with each client. Is there a built-in memory purge, or is there a preferred method to keep this from hitting a gig of used memory?
Thanks!
Labels:
- Labels:
-
Archive
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-31-2007 05:17 PM
Thanks for the quick reply Smikkel,
I guess when you give it a few gigs of RAM it's going to use it all it can. It will be nice to manage it more effectively though.
I guess when you give it a few gigs of RAM it's going to use it all it can. It will be nice to manage it more effectively though.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-31-2007 04:32 PM
Dotnet takes care of the memory and cleans it when it thinks it's needed.
In the next version I made some changes to manually clean the memory after each scan.
This means that a scan of 40 threads will take a maximum of approx 50 MB memory
In the next version I made some changes to manually clean the memory after each scan.
This means that a scan of 40 threads will take a maximum of approx 50 MB memory
