Software (On-Premises) Quick Trick for Keeping the Queue Clear

An easy way to keep Analysis Queue gridlock from happening when you inject a huge, many-day retroactive analysis into your routine, every-day profiles.

Be Sociable, Share!

Applies to:  WebTrends On-Premises, i.e. WebTrends Software


  1. Your WebTrends software has routine profiles that are scheduled to run every 4, 12, 24 (or whatever) hours
  2. You also have a one-time situation … you have to back-analyze a ton of retroactive data which will take many hours of WebTrends processing
  3. You don’t want the back-analyzing profile(s) to clog up the Scheduler and prevent the routine profiles from processing on time.
  4. You want to start the back-analysis profile(s) as soon as possible, but you want it/them to be out of the way when it’s time for the routine profiles to run.

There’s an easy way to keep gridlock from happening. 

Edit the back-analyzing profile(s) and  fiddle with Analysis Throttling and Scheduler as follows

In the Analysis Throttling admin panel:  (within the edit function of the individual profile)

  • Set “Maximum Data to Analyze” to be something that will take an hour or so to run.  For some profiles, this would be one day of data.  For others, it could be a month of data.  If you don’t already have an idea of analysis time for a day of data,  the Scheduler’s Job Status section can help.  Find the start and end time for the last run in the list of details.
  • Turn off “Rerun analysis immediately after maximum amount of data is analyzed.”  In other words, you want the profile to analyze for an hour or so, then close down (i.e. get out of the queue).

In the Analysis Scheduler: (again … you are doing this within the profile’s editing interface)

  • Set the analysis to happen every hour (the default setting is every day).

That’s all.  The only thing you need to do after the back-analysis profile(s) is finished is remember to set these settings back to normal, if you want that profile to continue to process new data  from now on.

How it works:  The back-analysis profile(s) will turn off after analyzing x days of data, whatever you specified in Maximum Data to Analyze.  At that point, everything in the queue moves up one step closer to the front … including your routine analysis event, which will the queue at its appointed time.  The Scheduler will put the back-analysis profile into the last position the analysis queue sometimes in the next 1-59 minutes.  The back-analysis profile will pick up from where it left off once it works its way to the front of the queue.


This method can cause some minutes’ delay in the start of the routine profiles compared to their scheduled time, but you gotta admit it’s far better than being stalled for many hours in the queue while the mammoth profile(s) continue processing. 

 This method also can delay the back-analysis profiles somewhat if you don’t find the right balance between Maximum Data to Analyze and Scheduler intervals. 

Be Sociable, Share!

3 thoughts on “Software (On-Premises) Quick Trick for Keeping the Queue Clear”

  1. Nope. That’s because once it gets into the active, processing state, no matter what priority it is, it’s going to stay active until it has analyzed everything and therefore be a clogger. The scheduler priority only affects how it rises while in the (inactive) queue.

  2. Good trick.

    Would lowering the scheduler priority when creating the back-analysing profile have a similar effect?

Leave a Reply

Your email address will not be published.