×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: Tom Liotta
Take care here -- most of what I wrote was in hopes of teasing
comments out from others. But, as you can see, essentially nobody
has anything to add.
I wish I knew more, too. Right now the auto tuner is allocating about 25% of system memory to the *INTERACT pool. But the only subsystem defined on the server pointing to that pool is QINTER, which isn't even running. Seems like a misappropriation of memory.
I just tested something. I pointed QHTTPSRVR to *SPOOL pool , and the subsystem that my Web applications run under to *SHRPOOL1. Then launched 70 separate instances of Google Chrome (the browser) and logged on to my Web portal from each. Then launched about 400 new Web application jobs from portal clients.
As new jobs were loaded, the auto tuner evidently allocated more memory to *SPOOL and *SHRPOOL1, gradually. With 70 portal sessions, 75 different Web applications, and 400+ application instances running, *SPOOL and *SHRPOOL1 grew from about 5 meg to about 60 meg each.
I used the jobs from each portal session to check performance, which was fine. I then left the jobs active, but idle for a while. The auto tuner gradually adjusted *SPOOL and *SHRPOOL1 back down to about 5 meg each. Then I began actively using the applications, and *SPOOL and *SHRPOOL1 increased to about 60 meg each, again.
It kind-of blows me away that a server supports 70 portal sessions, and 400+ jobs, using less than 2 meg per portal session - particularly when all the jobs are using SQL.
Contrast that with my PC, which has 2 Gig of Ram, where Windows gives me a daily reminder that virtual memory is too low.
Nathan.
midrange.com
