Home Forums Discussions Problems Slowdown with AC v7

from a previous thread:




Just wanted to post it separately instead of taking the other thread on a tangent.

Every computer connecting to the network is on a gigabit network with a gigabit switch (24 port). There are 4 computers at a second office that connect via terminal services over vpn

AC Server:
2x intel (6 cores each) e5-2630L v2 (2.4ghz)
48gb ram
4x1tb 6gb/s (raid10) - data
2x146gb 6gb/s (raid 1) - os

The terminal server is a separate server with 32gb ram and a 1gb connection

Again the issue arises on connecting the 10th user to AC.

there are a couple of possibilities.

Your setup seems very capable. It surpasses the basic requirements.

AC recommends that Terminal Services be on a separate computer than that hosting AC. The reason they give is that it is putting "stress" on the system and may slow it down.

I have a problem with speed (in 8.2.2) and have TS on the system. I will change this soon (possibly a month) to see whether this is, in deed, the culprit.

Thanks for your reply,

My terminal server is a separate computer.

I would start with going to SQL Express 64bit. This will free the RAM footprint some as SQL consumes some memory for each user. If SQL memory then balloons beyond 6-8G, your next option is full SQL.

For optimizing performance, there are a couple of other tweaks.
=> Go to SSD drive[s] for the AC database. We recommend RAID1, but there is a raw performance argument for single drives or even a PCI-E RAM disk for higher through-put.

==> Upgrade your RAID card to one with more throughput, caching and battery backup

==> Go to multiple NICs in cluster or segregate network traffic

These are all a bit more advanced, but it sounds like you might be up to it.

What would you think the order of most benefit would be? It still amazes me how resource intensive AC seems to be.

I would start with SSDs, whatever you can afford in a controller will help some.

Multiple NICs will also help, but they require more thought and configuration to achieve positive results.


Delivering large (500-1500 simultaneous user) client-server systems takes some real thought, design and skill in implementation. We have been doing that since the early 90s - it is hard work, and it always has been.

Add to that the constant addition of Meaningless Use, and the challenges only multiply.

That's fair enough - but this is a system being used by 10 users ... not 500-1500.

I have to look at Win 2012 some more; but NIC teaming seemed like a pretty straightforward process - my server has 4 GbE ports as is. Aren't there performance counters etc within the server OS to help diagnose where the bottleneck is?

My point was I know what it is like to create a larger multi-user systems. It is very different that the design for small systems. The key issue is that the the AC application is old enough, and low large enough, that the factors involved are several.

May I make a suggestion? Please tell me to shut up if it is not helpful. I find quotes to be helpful when used sparingly to address someone's previous point, but there are quotes in eight of the nine previous points. And, nearly all of them are quotes inside quotes inside quotes.

It just makes it very difficult to follow. Just a thought.

@ng12345 Please see my private message (PM)

We do this to make you see stars, Bert!

Wow, I do see stars. Never knew this before, but the program only allows you to do this four times in a row. Even the program knows!