> From: Nathan M. Andelin > > However, the Host Servers that you connect to (in my opinion) were not > designed for the dynamics of Web applications. A new host server job is > activated for each connection. Then after that, the stored procedure is > activated. After the run, the stored procedure is deactivated, > and the host > server job ends. It consumes significant CPU time. You run into > even more > difficult scalability issues than you do with CGI. I believe the latest version of the toolbox supports persistent connections, Nathan. In fact, there are a whole series of improvements to the JDBC architecture in JTOpen, enough to make it a viable alternative to client/server design, at least for an initial pass. This website has a number of suggestions: http://www-1.ibm.com/servers/eserver/iseries/toolbox/perfhints.htm#perfJDBC As you know, I'm not a JDBC advocate, but I think the toolbox team is trying very hard on performance. I don't know enough about it to be able to form an opinion as to their success. Joe
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.