I deployed my first website ( www.vfvbeheer.be ) build with EWB and a remote Dbisam database.  

Both the EWB webserver and the DBSRVR are working on my dedicated server and everything is running well.  

A backoffice application is working in the same remote database as the webapp.  The website is updated with the information retrieved from the Dbisam tables by means of querys.

I am just wondering if it could be a problem that about 500 users should be logging in nearly simultaniously on the webapplication.  Where could a bottleneck occur and can I do something to prevent a "meltdown".

Paul


Can't help with your question, and can't read the website but it looks nice.

Roy Lambert

<Paul Waegemans> wrote:
> I deployed my first website ( www.vfvbeheer.be ) build with EWB and a
> remote Dbisam database.  
>
> Both the EWB webserver and the DBSRVR are working on my dedicated server
> and everything is running well.  
>
> A backoffice application is working in the same remote database as the
> webapp.  The website is updated with the information retrieved from the
> Dbisam tables by means of querys.
>
> I am just wondering if it could be a problem that about 500 users should
> be logging in nearly simultaniously on the webapplication.  Where could a
> bottleneck occur and can I do something to prevent a "meltdown".

An interesting question. In my application, I used a timer to do calls to a
server that get the latest status. I found that if the server was slow
(usually me debugging) that the client web app would send multiple requests
and all get rather confused. Thus I put code in the client web app so that
it only makes one call at a time. If that takes ten years, then so be it.

How the built in updates work I do not know. Given how well Tim has thought
most things through, I am sure it is smart. Thus it comes down to mocking
the interface somehow to see how many queries the server can handle
simultaneously. And you can probably do a lot of that just by measuring the
time taken for the queries in multiple threads.

--
Matthew Jones

Paul,

<< I am just wondering if it could be a problem that about 500 users should
be logging in nearly simultaniously on the webapplication.  Where could a
bottleneck occur and can I do something to prevent a "meltdown". >>

If the application is mostly just reading data and doing occasional updates,
then no, you won't have any obvious issues with that many users.  There may
be situations where you run into bottlenecks, though, so you should be
prepared to do some logging/analysis in case you do hit such a bottleneck.

Nice job, btw - looks great and is very responsive.  But, be sure to
compress that application (Project Options/Compilation/Compress Output) to
make sure that the load time is as quick as possible.

Tim Young
Elevate Software
www.elevatesoft.com