We have never had scalability issues so far. Scalability can be handled by additional pollers, if and when required, to balance the load.

If the numbers are scary, then we can have multiple SAM instances based on geography or region or connectivity and use an EOC (Enterprise Operational Console) on top of it to collate the same.

We can also move the SolarWinds web UI/portal onto a different server when AWS (Additional Web Server) is used in conjunction with SAM.

SolarWinds is scalable if we procure more licenses. The scalable engine concept allows us to add polling engines for the new clients, so it's scalable in that sense. We have 400 users. 

It offers excellent scalability capabilities.

The solution’s scalability seems to be fine. We have around 8000 VMs right now and are not encountering any issues.

SolarWinds SAM is easy to scale.

The scalability of the SolarWinds Server and Application Monitor is good. However, if we consider the resources that are required to monitor the servers at times it can be too much.

The tool is scalable and I have customers who use it to monitor around 2000 servers. 

The scalability of SolarWinds Server and Application Monitor is good. We can add multiple scalable engines but they have performance issues most of the time.

I rate the scalability an eight and a half out of ten. Around seven employees are using the product in our organization. Our customers are enterprise businesses.

The solution is scalable, but not for large infrastructures. I can recommend SolarWinds for a mid to large scale organization. I am not convinced that customers who have two to four thousand devices and two thousand servers can implement SolarWinds on such a large scale.

The product is very scalable. No problem with that at all.  

Its scalability is pretty good. There are a lot of users using SolarWinds. They are mostly financial institutions. We are trying to bring in more people to make use of the product. So, we try to do a comparison to what they have presently and how we can optimize for them.

Scalability was an issue in the past. It wasn’t growing the environment, but rather it was maintaining it on upgrades. It used to take a long time since we have a large deployment.

Now that the lightweight scalability features exists, maintenance is not time consuming. Another issue was firewalls which is on our part due to “allow nothing, request everything” policy. No product out there will ever connect agnostically when it comes to firewalls.

Yes, there were issues with scalability. The polling engine can be a bit confusing as there are several conflicting statements regarding number of components, flows per second, Nodes, Volumes, and other variables that impact the polling engine performance.

In our case, the software stated we were at 65% of the available polling engine that was available. But we experienced monitors going into a hung state at random times.

This was finally determined by SolarWinds support to be due to the number of components we had active in SAM, even though SAM stated we were well below the acceptable number of components for our poller.

We added a second polling engine. (It is a super easy process to add additional polling engines.) SolarWinds has invested a great amount of time in the scalability expansion process, but the tool should reflect accurate info regarding the impact to the polling engine regardless of the source.

I ended up writing a custom SQL query to pull data points which gave us better polling data.

SolarWinds Server and Application Monitor is scalable. My company has 25 users. If you have more than 25 users, then you need to purchase an enterprise console. 

So far, we have been able to scale up to monitor everything we want without any issues. If we needed to poll more frequently, we would need to add additional polling engines.

In addition, the use of agents that can be deployed on local servers helps to offload processing from the primary poller.

We had scalability problems with the large number of PowerShell and WMI monitors.

We didn’t encounter any scalability issues for our infrastructure. We only have a 50 VM license and we are currently using 27 of them. We are not one of the larger enterprise environments. The speed and stability has been great.

Since 2012, we only had one major issue, and that is pretty good. If Windows were that reliable, what a world we would live in.

We haven't seen any restrictions on scaling. If a company needs to scale with this solution, they can do so.

The solution is scalable and you can add more devices. My company has 20 users for the solution.

We've found the solution to be scalable.

We don't have users per se on the solution, as it's only meant to monitor. We have seven people on our team, and any one of us can use the solution to check and monitor everything as needed.

We use it on a daily basis.

None

It is expensive to scale this solution, simply because of the cost of the polling engine. You can purchase unlimited IPs, but the price of an additional polling engine is $20,000 USD. That is quite a lot. We are looking into other solutions because it is just too expensive to keep scaling.

We have approximately eighty users and four hundred servers.

Scalability is good. It's modular, so you can just keep adding as you need it.

It is scalable. We have set up a lot of things, like 300 VMs and 10 to 15 different monitors. So, we are talking about a small number of monitors and a lot of VMs. It's kind of a big one.

It's very scalable. I installed it in a lot of companies. One had more than 1,000 users. There were no problems with it. We showed an internal team how to configure it for 100 devices and then they configured the rest of the 900.

Like any other vendor, SolarWinds recommend a maximum number of elements to be monitored by each polling engine. In case you have more elements to be monitored, you can deploy additional polling engines.

I managed to monitor more than 13,000 network elements using the main polling engine and four additional polling ones. It was really a great experience for me to handle all these engines with no problems.

This is a scalable solution. They have recently changed their architecture and now use horizontal scalable architecture using microservices.

It is absolutely scalable. We have worked on projects of different sizes for companies operating on local, national, and international levels. The smaller deployments include perhaps 10 network devices, 20 servers, and two network storage devices. We have done several medium-sized deployments with between 100 and 500 servers, including two data centers. 

There were no scalability issues, scalability has been easy.

No issues.

The solution is scalable. It's a license based scalability, but it is scalable.