DataGate’s connection pooling is a way to reuse existing server-side jobs for ASP.NET web apps. This is especially important on the IBM i, where creating a new IBM i job is relatively time-consuming. With connection pooling, a user can get a web page up in a matter of milliseconds, without connection pooling it could take up to a few seconds for a user to see a page.

This article provides the basics of understanding connection pooling:

Increase web app performance with DataGate connection pooling

This article provides help diagnosing connection pooling:

How find what ASPX page is causing orphan IBM i jobs

This article discusses how to limit IBM i jobs for ASP.NET Web sites

How to limit IBM i jobs in complex ASP.NET web apps