-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wicket,
wicket0123 wrote: | Since we cannot control anything that happens after a request leaves the | server, we want every request to be processed within 25 millisecods. The | order of execution is very simple: | | 1. Client send ad request with some parameters, hits a servlet. | 2. Ad server process the request which include app. code and talking to DB | 3. Ad server send response to client. the size of the response is roughly 2 | KB. If you're talking to a DB, this is likely to be the bulk of the time spent on the server. I assert (with no proof ;) that Tomcat's impact on your own code's response time is going to be a negligible percentage (unless you are using SSL, in which case you are screwed). How fast is your code already responding to these requests (without a servlet container adding any overhead)? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkftg3IACgkQ9CaO5/Lv0PB7aACgn43sMxldGO6BYWZ8m5S3XEFJ 9ngAoLWm0g0K/z8A/8gJ1V+pOKMeO1Xh =3KAk -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
