Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Webserver
Sun, Apr 22 2012 11:42 AMPermanent Link

Leslie

Tim,

The speed of he test server app you have made for the CDCollector demo  is quite impressive. At least when there is only one client.  I have not tested it with more concurrency because of the limitations of EDB trial. Is there a way I could create a test stress?  Any chance for separating the webserver from EDB?

Cheers,
Leslie
Sun, Apr 22 2012 11:57 AMPermanent Link

Leslie

I meant stress test

Cheers,
Leslie
Sun, Apr 22 2012 6:07 PMPermanent Link

Leslie

Tim,

I have created  a small test app to simulate concurrent users. It has a TWebbrowser which reloads the same simple  page when the document is completed. EDB server trial the test server is compiled with allows 3 concurrent connections, so I am running only two test apps. But even with these document loading never completes after a couple of reloads. With 3 tests running  the same thing happens almost immidiately. I suppose a single browser is using probably more then one connection.  

When I load the same page to a  browser myself while running the test apps it always completes. (IE, FF ,CH), but when I try to refresh, it often never completes in the browsers either.

Cheers,
Leslie
Mon, Apr 23 2012 12:33 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Leslie,

<< I have created  a small test app to simulate concurrent users. It has a
TWebbrowser which reloads the same simple  page when the document is
completed. EDB server trial the test server is compiled with allows 3
concurrent connections, so I am running only two test apps. But even with
these document loading never completes after a couple of reloads. With 3
tests running the same thing happens almost immidiately. I suppose a single
browser is using probably more then one connection. >>

Yes, most browsers will use up to 6 or so connections per session for
"general" loading purposes, but the server requests for the datasets are
serialized so that only one request is active at a time.  However, the image
loading from the EDB table on the other end is probably what is causing the
issue with too many connections since such loading *will* use the "general
loading" connections for loading the images from the URLs provided in the
dataset.

--
Tim Young
Elevate Software
www.elevatesoft.com
Image