From: John H. <web...@ew...> - 2007-08-30 03:33:07
|
Hi Jamie, I see collectinfo.pl running in the processes from time to time .... like maybe several times per hour? Anyway, I was wondering if you could shed some light on what this is doing. It does seem to be rather processor intensive for maybe 15 or so seconds like maybe every 5 or 10 minutes. Thanks, John Hinton |
From: Steve H. <st...@gr...> - 2010-04-27 02:34:06
Attachments:
smime.p7s
|
Can anyone tell me what on earth collectinfo.pl is doing that requires 200MB of *resident* memory on a little 64 bit debian VPS? That really is a bit excessive! Steve -- Steve Holdoway <st...@gr...> http://www.greengecko.co.nz MSN: st...@gr... Skype: sholdowa |
From: Jamie C. <jca...@we...> - 2010-04-27 04:28:40
|
On 26/Apr/2010 19:03 Steve Holdoway <st...@gr...> wrote .. > Can anyone tell me what on earth collectinfo.pl is doing that requires > 200MB of *resident* memory on a little 64 bit debian VPS? > > That really is a bit excessive! It collects stats that are used to display the virtualmin "system information" page that you see after logging in. 200M is rather high though - on my system, it peaks at around 55M. I could maybe believe that would double on a 64-bit system, but not quadruple! Unless you are running a really old virtualmin version. The underlying issue is that this script brings in all the virtualmin libraries, and libraries for a bunch of other modules too. I have a plan to address this by running these kinds of cron jobs inside Webmin's miniserv.pl process (which has already loaded the libraries), but haven't started implementing it yet.. - Jamie |
From: Steve H. <st...@gr...> - 2010-04-27 23:35:10
Attachments:
smime.p7s
|
On Mon, 2010-04-26 at 21:28 -0700, Jamie Cameron wrote: > On 26/Apr/2010 19:03 Steve Holdoway <st...@gr...> wrote .. > > Can anyone tell me what on earth collectinfo.pl is doing that requires > > 200MB of *resident* memory on a little 64 bit debian VPS? > > > > That really is a bit excessive! > > It collects stats that are used to display the virtualmin "system information" > page that you see after logging in. 200M is rather high though - on my system, > it peaks at around 55M. I could maybe believe that would double on a 64-bit system, > but not quadruple! Unless you are running a really old virtualmin version. No... all OS/*min is up to date. > > The underlying issue is that this script brings in all the virtualmin libraries, and > libraries for a bunch of other modules too. I have a plan to address this by running > these kinds of cron jobs inside Webmin's miniserv.pl process (which has already loaded > the libraries), but haven't started implementing it yet.. It's just a bit of a b*gger as that's more than the amount of free mem I have on this server, and it's forcing the use of swap which wouldn't otherwise be necessary... > > - Jamie Cheers, Steve -- Steve Holdoway <st...@gr...> http://www.greengecko.co.nz MSN: st...@gr... Skype: sholdowa |
From: Jamie C. <jca...@we...> - 2010-04-28 03:43:24
|
On 27/Apr/2010 16:34 Steve Holdoway <st...@gr...> wrote .. > On Mon, 2010-04-26 at 21:28 -0700, Jamie Cameron wrote: > > On 26/Apr/2010 19:03 Steve Holdoway <st...@gr...> wrote .. > > > Can anyone tell me what on earth collectinfo.pl is doing that requires > > > 200MB of *resident* memory on a little 64 bit debian VPS? > > > > > > That really is a bit excessive! > > > > It collects stats that are used to display the virtualmin "system information" > > page that you see after logging in. 200M is rather high though - on my system, > > it peaks at around 55M. I could maybe believe that would double on a 64-bit system, > > but not quadruple! Unless you are running a really old virtualmin version. > No... all OS/*min is up to date. > > > > The underlying issue is that this script brings in all the virtualmin libraries, > and > > libraries for a bunch of other modules too. I have a plan to address this by > running > > these kinds of cron jobs inside Webmin's miniserv.pl process (which has already > loaded > > the libraries), but haven't started implementing it yet.. > It's just a bit of a b*gger as that's more than the amount of free mem I > have on this server, and it's forcing the use of swap which wouldn't > otherwise be necessary... It is certainly much higher than necessary, and I suspect that being on a 64-bit system makes it worse. But I do have plans to address this in future though.. - Jamie |
From: Jamie C. <jca...@we...> - 2007-08-30 04:13:43
|
On 29/Aug/2007 20:32 John Hinton wrote .. > Hi Jamie, > > I see collectinfo.pl running in the processes from time to time .... > like maybe several times per hour? Anyway, I was wondering if you could > shed some light on what this is doing. It does seem to be rather > processor intensive for maybe 15 or so seconds like maybe every 5 or 10 > minutes. Hi John, The collectinfo.pl script is part of the Virtualmin module - it is run every 5 mins by default to gather system information like disk space, CPU load, quota use, package updates and Virtualmin domain counts. This is then used to generate the right-hand system information page that you see when logging in when using the Virtualmin theme. It is safe to adjust the cron job to run less often, but at the cost of the system information being less up to date. - Jamie |