|
Bugzilla – Full Text Bug Listing |
| Summary: | The zen updater suite devours my memory | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Ioannis Manoloudis <manoloudis4linux> |
| Component: | Zenworks | Assignee: | Chris Rivera <crivera> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Mauro Parra Miranda <mauro> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | andreas.hanke, ludwig, suse-beta |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | POST FCS PATCH | ||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
my process table
And some running stats |
||
|
Description
Ioannis Manoloudis
2006-07-04 10:48:41 UTC
Created attachment 92534 [details]
my process table
As you can see, the zmd suite takes nearly 2 GB of total memory.
Created attachment 92535 [details]
And some running stats
Here are some running stats from ksysguard.
I can confirm this problem. On Sunday, I had to kill resolve-dependencies; today, i had to kill update-status. Both occupied all available physical and swap space and thus caused the system to crawl. This is on a production server, so I need to do something about is as soon as possible - even if this means I have to install another distro. I don't know if it helps the developers to pinpoint the problem or if it is a distraction, but I also experience the problem described in bug 175150. The first screenshot you posted only shows vm size, which isn't what you want. RSS is what really matters. I'm working on memory profiling for the GUI tools at the moment. There are definitely improvements that can be made, but this is an on-going thing that we are always trying to improve. As for resolve-dependencies and update-status these are ZYPP helpers that are run by zmd. There are plenty of bugs open about their poor performance. the performace bugs are tracked in other items. Closing this one. *** This bug has been marked as a duplicate of bug 205164 *** |