general rule for best performance

ninap

hi, were wondering what or if there are any tips we should know about building apps with AwareIM. here are some of the questions which came up in a meeting.

Business Objects, is there any known limit or point in which the app will perform poorly (obviously we see bo's like tables and know bad erd can be bad)

Attributes, we have a BO with over 100 attributes and wanted to know
if this is bad design? most of the attributes are related

Rules, how many rules etc..

if anyone can give examples of what is too much or just poor design in relation to aware that could help us early on.

thank you - nina 🙂

himanshu

hi,

I think there should be no problem with creating as more as BO or its attributes we create in a application, if application designed nicely..(means keeping required information in correct order).

And most of currently performance is more depending on the system resources we are using.

I am working on such a application since purchased which keep on updating and increasing more BO, attributes are added as needs changes.

Currently ALL IZZ good going.

ninap

so if we had for example

100 BO's with 200 Attributes and about 20 rules per BO there should
be no issue running this on a 8 core, 16gb mem machine? nina

aware_support

Total number of BO's and attributes shouldn't matter. Total number of rules doesn't matter either, but the number of rules attached to a particular object can make a difference as far as performance is concerned, as rules attached to an object are executed when an object is created/updated. Also depending on how the rule is written, a particular rule can be very inefficient in particular circumstances.

You just need to check the performance of your application and optimise it if you have an issue. It is not the total number of objects, attributes and rules, but the rules themselves that can cause a slow down.

ninap

thanks for the response. we will keep a close eye on BO's with heavier Rule language which fires on create/update etc..

its the logging which we are concerned about as each bo of ours is required to track update/edit/delete for traceability..

thanks for the response. nina 🙂

BobK

aware_support wrote
Also depending on how the rule is written, a particular rule can be very inefficient in particular circumstances.

Can anyone provide any hints on writing efficient rules?

I have an object with 150+ rules, more than half are dynamic and populate fields base on what has already been entered by the user. There are also several relationships on this object. When creating this object, there is a noticeable delay between entering data in the first field and seeing other fields being populated.

Thanks in advance.

aware_support

Here are a few tips:

Optimisation of rules is about careful study of the LogViewer:

1) Check the Log Viewer for the execution of rules that refer to the object. These may be expensive. Execution of many of them may be unnecessary. Turn them off by going to the Advanced tab of the rule and ticking "Do not execute referred" (or something like that - the last checkbox there)

2) Aggregate operations (SUM, COUNT etc) can be expensive if you have lots of data. Try not to use them if you can

3) Unconditional rules can be expensive (especially if they use aggregate operations). Make them conditional (using WAS CHANGED expression, for example)

4) Check for repetitive execution of rules. The rule engine can execute rules repetitively if the next rule triggers a condition that causes the previous rule to fire again. Optimise this carefully. Use rule priorities to make sure that expensive rules are only executed once

pbrad

Well written Support. A good rule of thumb is that if your log viewer goes crazy for more than five to ten seconds after saving or creating an object, one of the tips above has been violated.

Tip #1 is something that I do by default now unless I know that I specifically want to check all referenced object rules every time I touch an object as it impacts so heavily on overall server performance.

From my experience, controlling the firing of rules is the number one way to speed up your apps and is more critical than any other aspect of your server or app.

Pete

leopdurr

I notice as my database grew my application get slow especially loading queries. when I start i had 20 record inside a BO now there are over 17,000 record and the performance of my system slow down. The server is running 8GB RAM Intel Core Processor.

Any suggestions?

I even increase my Memory setting to 1024MB Server, JBOSS 512MB and TomCat 512MB in AwareIM it slightly improve the speed.

aware_support

You need to do all the things recommended in this thread. If you direct your log output to a file you will see timing of rule execution. You can then pinpoint which rule(s) take long time to execute and optimise them.

If you have slow queries then you need to do the following:
1) Make sure that the query does not go through all records, for example this query is not a good idea for a large database:
FIND ALL Object
2) Indexing of attributes may help
3) If all else fails consider implementing your query as stored procedure