Webspeed and Appserver performances

[yves]

Dear all,

we are currently developing a product with Webspeed/Progress 9.1 technology. Some Progress specialists recommended that we use the Progress Appserver as well. Our software has been designed so it can fully work with the Appserver, e.g. it works with temp-tables for the communication between the Client and the Appserver. The UI is completely DB independent, which I beleive is the proper way to work and design WEB-enabled applications. It is possible to start the application without the Appserver active.

However, we are experiencing huge performance problems. Just going from on page to another or submit a simple query can take more than 10 sec, which is too much.

ISS, whith their TPT product does not use the Progress Appserver and it works very weel and quick.

Does anybody have an advice on the best way to develop a web-enabled application working with Progress Business Logic??? Is it the temp-table commincation model that takes so long????

Thanks,

Yves

 

[MurrayH]

WebSpeed

What you have to remember is that a WebAgent from WebSpeed, the AppServer Agent and the Progress Executable are essentially the same thing. Therefore, whatever your WebSpeed agent is doing, a Progress executable can do.

That aside, temp-tables is the way to go ... without a doubt. Progress is not good on client -> server comms over slow lines as it has lots of small packets so latency will kill you. What is the connection speed between WebSpeed and the database?? You must also use the "-Bt" parameter on the WebSpeed agents. This is essentially the "-B" for temp-tables so that temp-tables will be loaded into memory instead of off disk.

Aside from that we'd need to know what type of set up you have .. UNIX/NT, what comms, where is Progress .. what patch level, what web server .. etc. You are using IIS??

Murray