Forgive me for being naive....this is good to know. Thanks!
We need to invest in cluster and load balancing for this Witango app :-) MC. At 12:39 PM 3/20/2009, you wrote:
MC, Well, that's a big "it depends" Let's say you have 1 Witango service configured to handle 20 simultaneous threads on a single core/cpu server. Let's also say that your application take 1/10 of a second to execute when the server is otherwise idle. Therefore if you have 20 threads actively (simultaneously) processing your application, each instance will take 2 (20 * .1) seconds to complete (on average). Therefore if you send your server more than 1 request every 2 seconds, your server will not have the resources to keep up and will eventually crash (go unresponsive most likely) So what your server can do depends on what your hardware is and what your application does. In my setup, I've seen 10,000 people push my server to over 100 requests per second, but I have quite a bit of hardware, optimizations and experience to back it up. Robert -----Original Message----- From: MC Tay [mailto:sm...@media88.com] Sent: Friday, March 20, 2009 3:05 PM To: witango-talk@witango.com Subject: RE: Witango-Talk: 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:sm...@media88.com] >Sent: Friday, March 20, 2009 1:39 PM >To: witango-talk@witango.com >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:sm...@media88.com] > >Sent: Thursday, March 19, 2009 4:00 PM > >To: witango-talk@witango.com > >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 > > >rgar...@bighead.net - rgar...@eventpix.com > > >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
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
