This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Benefits of Additional Web Server

Hello,

I've been deploying and maintaining SolarWinds for the past 9 years and have never had the need to use an Additional Web Server (AWS) in any of my environments.  Right now I'm doing an initial deployment for a new company that will have about 50 concurrent users, and I'm wondering if I should look into purchasing the AWS license and install it on its own dedicated server.

We're still in the deployment phase, with a low number of users actually using it right now, so I'm unsure how to measure the performance gain with a dedicated web server.  Our environment has 2.3k nodes, 60k elements, and 4 Additional Polling Engines (APEs).  For modules we have NPM, NCM, SAM, and NTA.

Does anyone here have any experience with AWSs have any insight into the performance gain you've seen by splitting the web server off from the Main Polling Engine (MPE)?

Things I'm most curious on:

- What's the list-price for an AWS?  I can't find it on the North American Price Sheet.

- Is it possible to stack the AWS with an APE similar to how you can stack APEs with the MPE?

- At what level of concurrent users would a business typically purchase an AWS?

- If the MPE goes down for maintenance does that cause errors in the AWS, or can I reboot the MPE and still deliver the site to users?  Does AWS rely on the MPE?

Thanks in advance on any insight you all might have!

-Drew

Parents
  • Hi,

    I quick question a few month later on this thread:

    > can the Additional Web Server be used for the API in order to free the main poller from the load of the API calls ? this mean redirect our APIs call to the AWS rather than to the main server ?

    The more we integrate SolarWinds with other tools the more we need to call the API.

    Cheers

Reply
  • Hi,

    I quick question a few month later on this thread:

    > can the Additional Web Server be used for the API in order to free the main poller from the load of the API calls ? this mean redirect our APIs call to the AWS rather than to the main server ?

    The more we integrate SolarWinds with other tools the more we need to call the API.

    Cheers

Children
  • To my knowledge, unfortunately not. The SWIS endpoint for API calls is as far as I know on the main polling engine.

    cheers!

  • Actually SWIS exists on all SW servers that have the information service running, so the AWE does in fact provide that option.  The part where things can get ugly is the SWIS schema is not 100% consistent between the various flavors of orion servers, so querying against an AWE will give you slightly different tables compared to what you might see on the core server (i learned this the hard way).  Also there are cases I have run into where the AWE has problems with the messaging and sometimes doesn't display the same data as what I see in the main console.  So yes you CAN offload queries to an AWE, but there are things to be cautious about in doing so.  Ultimately all of the queries in SWQL end up translated back to normal SQL and execute on the database server, regardless of where you call them, so that still represents the ultimate bottleneck in terms how much you crank out of the API.

  • mesverrum thanks for the clarification. I wasn’t aware of that. Also thanks for the caveats.

    have to spin up a AWS in my lab and play with that.

    cheers!