RE: [Axapta-Knowledge-Village] Load balancing the AOS

Mon, 19 Dec 2005 10:22:56 -0800

I would just like to add a few things here so that we might be all clear on this subject as we help each other.
 
From my experience one slow AOS or Database server on the same network will slow down the entire system. This means that even if the database server meets and exceeds the required specifications and the AOS does not quite meet the specifications the whole system will operate at the same slow speed. The same goes for two AOS where one is better than the other, and even for slow client machines on the network that are actively using the Axapta Application. It is like a highway, with many lanes to accommodate heavy traffic (High Bandwidth), that narrows down to fewer lanes at a particular section (High Latency). This will result in slow moving traffic (for the entire highway) until the entire highway is designed to meet the demand of the traffic.
 
One fact about AOS from the Microsoft Official Training Material is as quoted: “Testing has shown than an AOS does not use more than 2 CPUs in the same computer as additional CPUs in separate servers. Due to the cost of Quad or larger CPU servers, adding servers is more cost effective.” This is self explanatory.
 
One important reason for using more than one AOS server is to provide fault tolerance that is not provided by two AOS services running on one server. If one server fails you should at least have another one to keep the application going until the other one is fixed. Hope this helps in some way.
 
Varden Morris
Senior Developer
WellPoint Systems Inc.
Suite 2000, 500 - 4th Ave SW
Calgary, Alberta, Canada
T2P 2V6
 
(403) 444-5848 direct
(403) 444-3900 main
(403) 615-1604 cell
www.wellpoint.ca


Brandon George <[EMAIL PROTECTED]> wrote:
Malcolm,
 
 Here is the post on the blog about this email: http://dynamics-ax.blogspot.com/2005/12/aos-load-balancing-when.html

From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Malcolm Burtt
Sent: Thursday, December 15, 2005 8:24 AM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: RE: [Axapta-Knowledge-Village] Load balancing the AOS

Feel free. Will I be famous? ;->

From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Brandon George
Sent: 15 December 2005 12:05
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: RE: [Axapta-Knowledge-Village] Load balancing the AOS

These are great tips! Can I have your permission to post these on my blog, along with your name, to give you credit?
 
-Brandon

From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Malcolm Burtt
Sent: Thursday, December 15, 2005 6:29 AM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: RE: [Axapta-Knowledge-Village] Load balancing the AOS

Hi Brandon
 
Well, I guess you'd look at the following...
 
1. Is my AOS processor bound and not able to take additional processors?
2. Is my AOS memory bound and not able to take additional memory?
3. Is my AOS network bound and not able to take another network card?
4. Is my AOS disk bound (unlikely on an AOS) and disk performance not able to be improved?
 
If the answer to any of the above is "yes" and your AOS machine is not providing ant other service that could be relocated to another server then you need to ask.
 
Is it more cost effective to add a new AOS (and cluster the two) or replace my existing AOS with a better specified machine that will not suffer the same resource deficiency? Note that, if your server is not memory bound but your Ax32Serv process has hit its 2GB memory limit then you are effectively memory bound. If your server has more than 4Gb RAM (i.e. enough for 2 x 2Gb plus sufficient for the operating system to continue to function) and the processor capacity to handle the extra load then you could consider adding an extra AOS instance on the same machine and clustering the two instances.
 
You might also consider that adding a newer AOS might result in a slightly imbalanced cluster. AFAIK The AOS load balancing picks the AOS with the least number of users on it. So, if you have two machines and one is newer (and therefore likely to be higher specified) its possible that users one the newer AOS will receive a better user experience than those on the older machine. Its not a particularly big problem but might complicate things for you as your needs expand again and the performance starts to dip for some users but not others (i.e. "why the hell is user A complaining when user B is not and why the hell did user B complain yesterday when user A did not").
 
Good luck
 
Malcolm Burtt
Touchstone
Our Trusted Solutions - Your Optimised Business

From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Brandon George
Sent: 14 December 2005 18:31
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: [Axapta-Knowledge-Village] Load balancing the AOS

Hello All,
 
 In light of my current progress to improve performance of Axapta, I am working through some idea's. I was wondering, what do you base load balancing for the AOS on? To explain further, what amount of users, or usage, etc. does one look at to say "You know what we need... we need to add another AOS and do load balancing!"
 
I am trying to find this out, but can't find much documentation on this. I am also really unsure of how to Google this topic, because it does not pull up much help.
 
Anyway, any advice on this topic would be great. Has anyone ever went from a single AOS to two AOS's load balanced?
 
thanks,
Brandon



Varden Morris
Senior Developer
WellPoint Systems Inc.

(403) 444-5848 direct
(403) 444-3900 main
(403) 615-1604  cell
www.wellpoint.ca
[EMAIL PROTECTED]

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Sharing the knowledge on Axapta.


YAHOO! GROUPS LINKS



Reply via email to