System Performance when moving from Interactive to Profound

[leatherlips]

Assuming a system is setup to process interactive workload. When implementing ProfoundUI and removing the interactive workload, what changes would be recommended (or "normal" to make)? Are there particular documents (Profound or other) that would help in getting the best performance when switching to an HTTP server handling the user workload?
Any information would be helpful, as most companies with iseries/IBMi systems don't have a team of System administrators/performance experts on staff(part of the benefit of running the "i")

[David]

Are you using Genie as well? When using Genie, your application sessions still run in 5250 interactive jobs.

If not running in Genie, then everthing runs in batch. If getting rid of the interactive workload, you'd want to do things like:

* Ensure that the system's memory pools are configured to allow plenty of memory for batch jobs -- it may be mostly allocated to interactive jobs as it stands.

* The job run priority may be higher for interactive jobs.

* If you're getting a lot of memory page faults, you may need to add more memory to the system. Running under the http server uses more memory than 5250 interactive jobs.