Memory Optimization Question

twhitehurst

OK, I understand where and how to set memory, but my question is (and I know it is a little open ended)

"Is there some formula to setting memory to be the most optimized?

Here is why I ask.

I have an Aware Application that is:

Running on Derby Database
Running on a Windows server with 4GB of RAM
Hosted at Go Daddy
Server ONLY runs aware and a version of MS Office for document/report creation
Current Database size is about 6GB (and growing daily)
The application has a lot of file attachements Example I have a BO called "Project" and a BO called "Inspections" and a BO called "Maps"
Inspections and Maps are created daily and uploaded as attachements
The Project BO pulls in a listing of Inspections and Maps associated with the Project based on one to many relationships
Example of size: Total Inspections to date about 15,000
I run most queries to be based on the LoggedInRegularUser so basically IF LoggedInRegularUser=Project.InspectorName (or queries such as this to filter data)

It takes an average of 30 seconds (sometimes longer) to open any Project, Inspection, or Map. While simple queries like All Regular Users can take an average of 5 seconds.

My Current Memory Settings (and I've played with a lot of them) are:
Aware Server 500MB
Tomcat 500MB
JBOSS 500MB

I would like to hear how others are setting memory or any wisdom associated with this subject.

Thanks in advance.

twhitehurst

Also, I forgot to mention that in the application I talk about above I am doing a lot of indexing. So, I don't think this is an issue, but I am open to any and all ideas, suggestions and hopefully solutions 😛

aware_support

This is unlikely to be a memory problem. The fact that a simple query for RegularUsers takes 5 seconds suggests that you most probably have a slow connection or you have some kind of a slow down on the server. I can't see how Aware IM can slow down such a query. Try running it on a local machine and it will be very fast.

With other objects it is possible that you have many references between objects, so that when you display a form it tries to pull all these references from the database. Consider putting references on a separate tab.

twhitehurst

I guess I should restate the question.

:?: 1. "Is there a formula or good "rule of thumb" used for the most optimized memory settings on an Aware Server"?

and I would also add.

:?: 2. "Is there a "BEST" configuration to get the most out of Aware. (Example: In a perfect world how would you configure Aware? What Server OS would you use, What memory settings would you use? What Program would you use to create documents & reports (MS Office or something else?), What database would you use?

What is the BEST configuration possible?

I am continuing to work to optimize my application and I'm willing to even move it to another server and change configurations, but need some idea fo direction before I do this.

:arrow: One other question while we are discussing optimization.

I do a lot of indexing in my application. When does aware build or rebuild indexes?

:?: If I have a large amount of data and users constantly updating the system with new information. How does the indexing process effect application speed or server demand?

Thanks

ACDC

It would be very interesting to see if you get better performance using a MYSQL database engine.

aware_support

There is no formula. The more memory the better. In the real world the amount of memory you allocate depends on the nature of your application. Please see the Installation Guilde and also this forum for considerations on when to allocate more memory to different Aware IM components.
In the perfect world you would choose the most powerful database and maximum memory. OS almost doesn't matter. Discussion on what database is the most powerful is beyond the scope of this forum. In our tests SQL Server was the best, followed by Oracle and MySQL
Aware IM builds indexes when a configuration is published. Again database indexing topic is beyond the scope of this forum - there's plenty of literature available. Indexes significantly improve performace of queries that use indexed attributes, but they may slow down inserts and updates (creating and modifying new objects).