lol, y, that is what it means. Your witango config, probably only
allows 15-30 threads at once, plus you have a connection limit of
around 50, then there is the limitations of the webserver and how it
is configured. Then there is the amount of resources an app takes. If
you have a page that is just serving some light html, maybe a couple
of simple variables with no db connection, a decent witango setup of
one server can handle several hundred thousand page views to maybe a
few million page views a day, depending on how they are spread out.
Then you start adding loops, and processing within loops, then db
connections, some expensive TAF applications, can be such that you
could only run 10000 page views a day, and no more than 4 or 5
simultaneously. There are so many variables and it is not an exact
science. This is where setting up a cluster or load group also becomes
essential.
You can't just throw anything at it, and expect it to work, it is like
taking your honda prius, and hooking up your 10,000 lb boat and
expecting it to go when you hit the gas.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[email protected] - [email protected]
http://bighead.net/ - http://eventpix.com/
On Mar 20, 2009, at 12:04 PM, MC Tay wrote:
Hi Robert:
Does that mean Witango application cannot support millions of users,
with the possibility of 5000 users hitting the site at almost the
same time?
Thanks!
MC
At 10:58 AM 3/20/2009, you wrote:
If you submit 5000 requests to your Witango server at nearly the
same time,
you will likely crash it. There is no good solution here. You may
have to
rethink your process. Robert
-----Original Message-----
From: MC Tay [mailto:[email protected]]
Sent: Friday, March 20, 2009 1:39 PM
To: [email protected]
Subject: Re: Witango-Talk:
Thanks for your suggestion Steve.
It works if we put a <@sleep> of at least 1 second in file1.taf.
However, that defeats our purpose of not waiting for the results
from file2.
We need file1.taf to finish the loop quickly (it could be a loop of
over 5000). We want file1 to create many sub-processes, say in this
case 5000, of file2.taf....and let file2.taf take it's time to do
whatever it needs to do.
To answer your question, no there's no other user, domain or
application vars that shares between file1 and file2......there're
all local vars.
Thanks!
MC
At 07:45 AM 3/20/2009, you wrote:
>Maybe you should try a <@sleep> in file1.taf to give file2.taf a
>chance to start execution?
>
>Also are there any user, domain or application vars in either taf
>that might cause file2.taf to think it is done?
>
>Just a couple thoughts.
>
>Steve Fogelson
>
>-----Original Message-----
>From: MC Tay [mailto:[email protected]]
>Sent: Thursday, March 19, 2009 4:00 PM
>To: [email protected]
>Subject: Re: Witango-Talk: Non-asyn call in Witango
>
>Thanks Robert...that works.
>
>However, I have a loop of say 50 in file1.taf triggering <@URL> to
>file2.taf. For some reasons the <@URL> to file2.taf ran 9 times only
>even though file1.taf completed the loop of 50.
>
>Any idea why?
>
>Thanks!
>
>MC
>
>At 11:15 AM 3/19/2009, you wrote:
> >you can do @url, and tell it not to wait.
> >
> >--
> >
> >Robert Garcia
> >President - BigHead Technology
> >VP Application Development - eventpix.com
> >13653 West Park Dr
> >Magalia, Ca 95954
> >ph: 530.645.4040 x222 fax: 530.645.4040
> >[email protected] - [email protected]
> >http://bighead.net/ - http://eventpix.com/
> >
> >On Mar 19, 2009, at 11:09 AM, MC Tay wrote:
> >
> >>Hi:
> >>
> >>We have a situation that needs file1.taf to call file2.taf
without
> >>having to wait for the results from file2.taf. Is there a way
to do
> >>this?
> >>
> >>Thanks!
> >>
> >>MC
> >>
>
>
>
________________________________________________________________________
> >>TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>
>
________________________________________________________________________
> >TO UNSUBSCRIBE: Go to http://www.witango.com/developer/
maillist.taf
> >
> >
>
>
________________________________________________________________________
>TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
>
>
________________________________________________________________________
>TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
