Actionsite size problem - performance impacted

Usage and Config Platform
1

(imported topic written by jfschafer)

I noticed that our actionsite was getting large. (from the Deployment Health Dashboard). I had about 20 actions (basically agent and relay settings) assigned to the entire infrastructure as a policy action for all new agents and relays. I did this under the master operator account which I discovered is not the recommended account to use. After stopping the actions I created another non-master operator that has the ability to assign actions to all systems and put the actions there. I also moved 3 automatic groups that I made under the Master site as the master operator. However, the actionsite size still says it’s 35 MB or so. So I navigated to the
location of the actionsite files (C:\Program Files (x86)\Bigfix Enterprise\BES Server\wwwrootbes\bfsites\ and went to the latest actionsite folder which happens at the time of this writing be actionsite_0_1174. The size of this folder and all it’s contents is indeed the 35 MB in size. Navigating inside I see a ton of efxm and FXF files that coorespond to the external sites both subscription and "unsubscription for .fxm, each range in size anywhere from 7-82 KB in size each. Total size of just those files is 27.5 MB and there’s a total of 506 of those files in my latest actionsite folder. It says you want to keep the actionsite small, so how can you do that when the default sites that come with Bigfix are placed in the actionsite making it at least 25 MB ??? Is there any way to move them somewhere else?

So the knowledgebase article on the actionsite size says nothing about these site subscription and unsubscription files. Looking overall how to keep the actionsite size small, because when it gets large, clients don’t join groups, take forever to evaluate actions/relevance and just overall slow everything down, not to mention the 100’s of relays have a hard time keeping up with the latest actionsite version. (which is also going on).

Any tips?

2

Any progress on this? We are seeing the same thing. On a related note, our enterprise security site is at 94 MB with 132 files and BES Support is at 71 MB with a whopping 1,324 files. Every single console operator that uses our shared terminal server gets these files put in their Appdata\BigFix\Enterprise Console directory, which I’d assume slows delays the console load process.

3

There is no other place where the subscription actions and mastheads to subscribe with can go yet. We have been thinking of ways to help the situation but have not yet come up with a solution. We should be dynamically changing the warning based on the number of sites your console has visible so that is something we can do.

Mentioned were 27.5MB of subscription information so there is about 10MB of other stuff. Global analysis activations are also in there as are the properties files.

We did make some changes in the past to collapse the Analysis and Questions FXF files into a single file so not sure if this is in the version mentioned but most people should see the number of files shrink. An additional issue was the introduction of SHA256 mastheads which made those EFXM files even bigger.

@rkalnoskas how big is your actionsite?

4

Our actionsite is just shy of 20MB on 9.1.1229, which doesn’t seem too bad. I was looking at this from a console operator standpoint - clients seem to be processing normally. We just found and removed 400MB of files (seemingly incorrectly) added to sites via the console, so that will be a substantial reduction of content imported upon console load for 100+ operators.