This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Publisher
- :
- FlexNet Publisher Forum
- :
- BUG: (P1) Significant memory growth of lmgrd
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 17, 2005
08:00 PM
BUG: (P1) Significant memory growth of lmgrd
We did some memory size monitoring, and it seems that the 10.8.1 lmgrd has significant memory growth over periods of time. We re-checked the 9.5 lmgrd and confirmed that it did not have this problem.
Here are the methods of our test:
The environment and scenario were exactly the same in both cases.
1. lmgrd and VD are installed on hostA.
2. After lmgrd starts up we are checking how much memory it uses:
for lmgrd 9.2:
ps axuw | grep ./lmgrd
tgrabows 20413 0.0 0.0 2044 988 pts/0 S 16:55 0:00 ./lmgrd -c license.dat
which means lmgrd uses 2044 kB of memory
for lmgrd 10.8:
tgrabows 31376 0.0 0.0 2624 1196 pts/0 S 12:54 0:00 ./lmgrd -c ../counted.platall
which means lmgrd uses 2624 kB of memory
3. On hostB we are starting 30 times per second our "friendly" program. Everyone of them requires 1 license to work. Runtime is random from 1 to 5 seconds.
4. After 5 minutes we are checking how much memory lmgrd uses:
for lmgrd 9.2:
tgrabows 20413 0.4 0.0 2044 988 pts/0 S 16:55 0:02 ./lmgrd -c license.dat
which means lmgrd uses 2044 kB of memory (no change)
for lmgrd 10.8:
tgrabows 31376 0.4 0.1 5448 3928 pts/0 S 12:54 0:02 ./lmgrd -c ../counted.platall
which means lmgrd uses 5448 kB of memory (changed from 2624 kB).
The detailed results of our tests are tabulated in the chart.jpg file attached to this post.
In summary, the 10.8.1 lmgrd grew from 2.5 Mb to 5 Mb in 5 minutes, while the 9.2 lmgrd stayed more or less around 2 Mb. We also repeatedly tested 10.8.1 lmgrd with either 1 or 5 vendor daemons, and the growth in memory can be consistently observed.
-Johnson
Here are the methods of our test:
The environment and scenario were exactly the same in both cases.
1. lmgrd and VD are installed on hostA.
2. After lmgrd starts up we are checking how much memory it uses:
for lmgrd 9.2:
ps axuw | grep ./lmgrd
tgrabows 20413 0.0 0.0 2044 988 pts/0 S 16:55 0:00 ./lmgrd -c license.dat
which means lmgrd uses 2044 kB of memory
for lmgrd 10.8:
tgrabows 31376 0.0 0.0 2624 1196 pts/0 S 12:54 0:00 ./lmgrd -c ../counted.platall
which means lmgrd uses 2624 kB of memory
3. On hostB we are starting 30 times per second our "friendly" program. Everyone of them requires 1 license to work. Runtime is random from 1 to 5 seconds.
4. After 5 minutes we are checking how much memory lmgrd uses:
for lmgrd 9.2:
tgrabows 20413 0.4 0.0 2044 988 pts/0 S 16:55 0:02 ./lmgrd -c license.dat
which means lmgrd uses 2044 kB of memory (no change)
for lmgrd 10.8:
tgrabows 31376 0.4 0.1 5448 3928 pts/0 S 12:54 0:02 ./lmgrd -c ../counted.platall
which means lmgrd uses 5448 kB of memory (changed from 2624 kB).
The detailed results of our tests are tabulated in the chart.jpg file attached to this post.
In summary, the 10.8.1 lmgrd grew from 2.5 Mb to 5 Mb in 5 minutes, while the 9.2 lmgrd stayed more or less around 2 Mb. We also repeatedly tested 10.8.1 lmgrd with either 1 or 5 vendor daemons, and the growth in memory can be consistently observed.
-Johnson
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 17, 2005
08:06 PM
It's not clear whether this behaviour is a result of the integration work or something in 10.8 which our deliverable is based. Either way, it represents a serious problem to an enterprise level deployment (that these test cases were created for).
Greg
Greg
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 17, 2005
08:17 PM
Hi,
Two things:
9.5 and 10.8.1 are very different releases; so an apples-to-apples comparison doesn't make sense.
Secondly, the last drop (RC1) that Lars sent out is the integrated 10.8.x build. Please run all your tests against the new build and report any issues.
In the meantime, we will investigate if there are memory leak issues associated with the 10.8 release line.
---Jagan
Two things:
9.5 and 10.8.1 are very different releases; so an apples-to-apples comparison doesn't make sense.
Secondly, the last drop (RC1) that Lars sent out is the integrated 10.8.x build. Please run all your tests against the new build and report any issues.
In the meantime, we will investigate if there are memory leak issues associated with the 10.8 release line.
---Jagan
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 20, 2005
02:48 PM
We have replicated the problem in the rc1 release delivered to us on Fri June 17th.
Over the weekend, we have seen the daemon grow to over 500 MegByte
The comparison to v9.5 was based on a known "stable" release. Whether we considers them comparable or not is debatable. Certainly this level of memory usage/growth will make 10.8.x unusable in the target accounts.
Greg
Over the weekend, we have seen the daemon grow to over 500 MegByte
The comparison to v9.5 was based on a known "stable" release. Whether we considers them comparable or not is debatable. Certainly this level of memory usage/growth will make 10.8.x unusable in the target accounts.
Greg
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 20, 2005
04:18 PM
I just confirmed the problem with engineering. There is a memory leak in the 10.8.x lmgrd which they have already fixed. The fix will be included in the 6/24 release.
Lars
Lars
