[revServer] process timeout issue

Pierre Sahores psahores at free.fr
Mon Aug 2 17:23:36 CDT 2010


Thanks for testing Andre !

Your tests confirms mine and the tools.pingdom.com  ones <http://tools.pingdom.com/?url=www.woooooooords.com&treeview=0&column=objectID&order=1&type=0&save=true>.

Kind Regards, 
Pierre


Le 2 août 2010 à 18:09, Andre Garzia a écrit :

> Pierre,
> 
> I've just run 25 concurrent clients for 30 seconds against
> wooooooooords.comand no request failed. The report is as follow:
> 
> Transactions:                  81 hits
> Availability:              100.00 %
> Elapsed time:               29.82 secs
> Data transferred:            4.21 MB
> Response time:                8.35 secs
> Transaction rate:            2.72 trans/sec
> Throughput:                0.14 MB/sec
> Concurrency:               22.67
> Successful transactions:          81
> Failed transactions:               0
> Longest transaction:           15.59
> Shortest transaction:            3.39
> 
> You can see that the response time and transaction rate is pretty bad but
> this is probably due to my bad network but the good news is that your server
> sustained 25 concurrent clients for 30 seconds with no hiccup. You can also
> notice that there were requests that took 15 secs and others that took 3
> secs, which is odd since they were all hitting the same page.
> 
> What we can infer from this simple thing is that there are places that
> RevServer needs working but it also means we need more focus to find where
> and why it breaks.
> 
> Andre
> 
> On Mon, Aug 2, 2010 at 12:54 PM, Pierre Sahores <psahores at free.fr> wrote:
> 
>> 
>> Le 2 août 2010 à 16:51, Jerry Daniels a écrit :
>> 
>>> Sarah and I are unhappy with the performance because we load test it and
>> see some requests take many seconds to complete and then the next identical
>> request takes less than a second.
>> 
>> Exact : i can see this happen with the early requests to woooooooords.com: The first request can, time to time, take around 20 secs. to get it's
>> response back to the end-user's browser. After this first request, the next
>> ones are always back to the user in less than some ticks. Could be a problem
>> related to the RAM virtualisation of the RHEL5 host it self, httpd.conf,
>> etc... and, please RunRev, we all need to get this fixed.
>> 
>> Best, Pierre
>> 
>> --
>> Pierre Sahores
>> mobile : (33) 6 03 95 77 70
>> 
>> www.woooooooords.com
>> www.sahores-conseil.com
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>> 
> 
> 
> 
> -- 
> http://www.andregarzia.com All We Do Is Code.
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
> 

--
Pierre Sahores
mobile : (33) 6 03 95 77 70

www.woooooooords.com
www.sahores-conseil.com







More information about the use-livecode mailing list