Re: [Axapta-Knowledge-Village] how to minimize blocking on axapta ?

Mon, 07 Mar 2005 03:16:57 -0800

Hi Sas,
 
Please let us know the cause of your problem when you look at the code.

SAS <[EMAIL PROTECTED]> wrote:
Dear Verden ,
In my opinion , as long as the disk performance is not bottle neck ( ex. Avg disk queue lenght  <= 2 X number disk ) it is not necessary to modify raid configuration.
for memory , we already enabled AWE memory .
thx
sas
 
 
 
----- Original Message -----
Sent: Saturday, March 05, 2005 1:24 AM
Subject: Re: [Axapta-Knowledge-Village] how to minimize blocking on axapta ?

Hi Sas
 

The hardware looks good to me, away from the RAID 5 for the database. RAID 5 does not give good performance for writing since it involves the calculation of parity. I made a mistake in my first email to you. We do not use RAID 15 but RAID 10. RAID 15 also involves parity. It is a combination of RAID 10 and RAID 5. RAID 10 is a combination of RAID 1 (mirror) and RAID 0 (striped). You only use 50% of your storage but you get good performance for writing.

 

Did you configure windows and SQL to see 3G of memory and over? There are some tools that you can use to find the exact problem. They are costly but they work. Spotlight for SQL and windows work well. It shows up all the flaws. Our consultant used it to solve our problems and we are currently in the process of purchasing the software. Sometimes the log file disk could be running out of space and you don’t know and this slows down the entire system. The problems are endless and many.

 

The code could very well be a problem too. Have you done a lot of customization? If this is the case you may have code that is inefficient.



SAS <[EMAIL PROTECTED]> wrote:
Dear Verden,
my Hadrware configuration , Database server , 4 Proccessor 3.0 Ghz , 8 GB RAM , Quorum : 2 Disk raid 1,  Tempdb 2 Disk raid 1 , database 7 Disk Raid 5 , all disk are Fibre channel  2 Gb disk 15K rpm . For application server 2 Proccessor 3.0 Ghz , 2 GB RAM .Concurent user 70 users .
I tought my hardware configuration are enough , So I suspect it's bacuse our coding .
my experience tuning hardware , OS and  SQL server only give 10% improvement, table indexing also improve the performance . and now we are investigating our coding.
thx
sas
  
----- Original Message -----
Sent: Friday, March 04, 2005 12:58 AM
Subject: RE: [Axapta-Knowledge-Village] how to minimize blocking on axapta ?

Hi Rocco

 

If disk queue and swapping are acceptable for the object server during peak periods this should be an indication that the object server(s) is ok. We had 1G of memory and two Pentium III processors in two object servers. The disk queue was high as a result of the processors not being able to adequately manage the requests from the clients. Also, there was a lot of swapping resulting from the memory not being enough. For some reason this resulted in the database locking up.


Rocco Giumelli <[EMAIL PROTECTED]> wrote:
Hi Varden
 
Can I ask, We have recently upgraded our SQL Server, But the application server we didn't becasue when I look at the task manager the machine does not do much, system idle is running 90% + , and the Networkwork interface runs at less than 10% on 100 link most of the time. Has Scsi Hard Drive.  It indicates to me that an upgrade is not needed.. Would you agree?
 
Rocco

From: Varden Morris [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 2 March 2005 7:59 PM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: Re: [Axapta-Knowledge-Village] how to minimize blocking on axapta ?

The two main things I know can affect blocking are hardware and code.

 

I have experienced major blocking as a result of hardware. I understand the technical concept involved but I do not have all the details at hand.

 

You can use one server as the application and database server but this may not be ideal for your situation. The best configuration for top performance is at least one database server with a SAN unit for the data and an application server that may also be the object server if you are going 3-Tier. You may optionally use a different server for the object server. One object server should be adequate for up to one hundred users. Over that you may use two in load balancing mode.

 

Now blocking can be a result of the existence of a bottle neck with your hardware. The client in a 2-tier configuration and the object server in a 3-tier configuration constantly make requests to your database sever that include reading and writing of data. The communication link between the client/object server in such a situation needs to be high speed (I believe fiber may be the best medium). In addition to this the internal speed of the disks (you also have fiber disks) it also important. When requests are made to the database server the disks need to be able to process the requests as fast as possible otherwise one request may be waiting on another to be completed which results in blocking. Several of this may occur that lead to severe blocking.

 

The storage unit for the database should also be a combination of RAID 10 and RAID 15. RAID 10 is just striping while RAID 15 is a mirror of a RAID 10. Since the data files are very important you should but then on the RAID 15 and since the temp database and log files are not so critical you should put them on RAID 10. This will speed up the read/write process for the database and thus reduce blocking. RAID 5 saves you space but it is not ideal for read/write intensive operations since the process involves parity calculation.

 

The technology of the quad processor is advanced and can help in a big way. I do not know the details about this but I know it works.

 

If the specification of the application sever is not good enough this can also lead to blocking. I have personal experience where the database server was upgraded and the blocking was still the same. After upgrading the application server there was a major difference.

 

You must always have enough memory in your servers to ensure that there is not much caching. When you have over 3G of memory you need to enable windows to use it. You also need to enable Microsoft SQL to use over 3G (if you are using MSSQL).

 

The last thing is coding. You should ensure that transactions in the application are short. This means ensuring that you use tts.begin and tts.commit or tts.rollback in very short blocks of code where it is necessary. Otherwise tables/records may be locked in a waiting transaction that results in major blocking.

 

Hope this will be of some help to you.

 

Varden Morris

 

J. Wray & Nephew Ltd. - Group I.S.

234 Spanish Town Road

Kingston 11, Jamaica, W.I.

 

Phone:  (876) - 923 - 6141 Ext. 2226
Fax:      (876) - 923 - 5372

Cell:      (876) - 3833566
Email:   [EMAIL PROTECTED]

            [EMAIL PROTECTED]



SAS <[EMAIL PROTECTED]> wrote:
Dear all,
Do you have any experience how to minimize blocking on axapta ?
would you mind sahring your experience,
thx
sas




Sharing the knowledge on Axapta.


Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web

Sharing the knowledge on Axapta.




Sharing the knowledge on Axapta.


Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web

Sharing the knowledge on Axapta.




Sharing the knowledge on Axapta.


Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web

Sharing the knowledge on Axapta.




Sharing the knowledge on Axapta.


Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web

Sharing the knowledge on Axapta.


Yahoo! Groups Sponsor
ADVERTISEMENT
click here

Yahoo! Groups Links

Reply via email to