Thoughts on Optimization - Make your app "Production Ready"

BenHayat

Firstly, thanks to Support for that great Optimization video.

Working on app optimization now. Going through all the rules to see if I can revise "Cross Reference" rules to "On -demand" process rules.

Sometimes when I have loops within loops that have cross reference rules, it can really bring the system down (Not aware's fault, just how it works), now I'm investigating aggregate & cross reference rules of objects that are specially involved in loop processes.

My app has simple UI (but a lot of work behind the scene). After two years of development, I need to put it under microscope to make sure it's fully optimized.
This past weekend, I optimized a process that used to take 90 seconds (for 30 replications) to 42 seconds, and now I see there are several cross-reference and aggregate rules in those inner loops that create ripple effects and use a lot of CPU and Disk I/O. If I can optimize these rules properly, I can speed up the replication process, which is very resource hungry.

I thought I share this with others to look into these two type of rules that are expensive and resource hungry especially in loops.

kklosson

I have been undertaking similar efforts. One of the first things I've run into is that a lot of my cross-referenced rules are protection rule. It occurs to me, should any protection rules check referred attributes? Although I have watched the vid several times, I am not perfectly clear on when you would actually want to check referred objects vs. not wanting to. So it seems the default perspective would be to not check a referred attribute unless there was a compelling reason, but I do not know the compelling reason. So rather that understanding when NOT to checked referred attributes, I wonder when DO you want to check referred attributes. I hope this topic goes long...

BenHayat

Now that my app is generally completed, except the final part of payment processing, and I wrote many rules that did the job at the time I was writing a particular process or module to get it to work.

Now, that everything works, I need to make it "Production ready". I'm stepping back and literally drawing workflow of the already built system (to give me a 30,000 feet view) and see, are there any repeat loops (by aware engine) that I can smooth out.
Yesterday, I spent the whole day and cleaned up all my nightly emails and their filters and making sure those queries were optimized. Added a few indexes too.

Love to hear from others what steps they take to make their app "Production Ready".

johntalbott

End user testing to:
-identify any bugs that have been missed
-get feedback on the UX of the application
Load testing so you know what your "breaking point" is in a proactive manner

tford

1. End user testing to:
-identify any bugs that have been missed
-get feedback on the UX of the application

Much like John, I have a select group on users that help me find bugs or UI issues with the application. My approach is to not give them much direction & watch what things are not intuitive to them or cause questions / confusion. I go though iterations of this through the process of building an app. That's the beauty of using AwareIM to develop .. those cycles between user feedback & fixing / developing can be pretty tight windows.