Is there a timeout option for webreports?

Reporting
1

(imported topic written by lmpymilk91)

We have a large number of machines and sometimes our reports can be very large in size causing our webreports to run out of memory many times a day. I am wondering if the web server is timing out and this is causing it to hold on to the allocated memory and not releasing it after the timeout.

Thank you

2

(imported comment written by BenKus)

Hi lmpymilk,

Can you give us a sense of how many computers you guys have? There are definitely steps you can take to help this, but I am trying to get a sense of your deployment size…

Ben

3

(imported comment written by lmpymilk91)

number of bes computers = 229069

4

(imported comment written by BenKus)

Ah… So you weren’t kidding about having a very large deployment. :slight_smile:

When you get to 200,000+ computers in your deployment, you really start to need to maximize the memory available to your web reports. Here are some key pieces:

  • Make sure your web reports is on an x64 system. This will allow it to use 4GB of memory before it runs out of adressable space.
  • Make sure you have at least 6 GB of memory on the web reports server.
  • There is a settng you can use to exclude some of your previous Fixlet result history (which can save a lot of music):

HKLM\SOFTWARE\BigFix\Enterprise Server\BESReports

FixletResultCheck (String) = 1

FixletResultBeginDate (String) = 2009-09-01 00:00

Filters out Fixlet Results which are not currently relevant and last became non-relevant before 2009-09-01 00:00

But… I would say that you should contact our services team and do an optimization checkup on your infrastructure (I believe that you guys have an existing services contract in place).

Ben

5

(imported comment written by lmpymilk91)

the x64 hardware is on the way so I sure hope it will be better.

as for the memory, if you look at the logs it looks like the there is no memory release.

right now we are using version 7.0.9.164 are there any optimizations for webreports in the newer versions?

6

(imported comment written by BenKus)

The web reports keeps around in memory a certain amount of info about the computer and Fixlets and you have a lot of data that it needs… When it runs out of memory, it is because Windows tries to allocate a memory block, but there isn’t a biggest enough free memory block because the addressable space is filled and somewhat fragmented by the naturalway memory management works.

I believe the newer versions of BigFix have some memory optimizations for high-scale web reports deployments… and there are lots of reasons that you should upgrade…

Ben