And, in my experience, most of both the end-users and Google don't like to wait more than 6-8 seconds for an acceptable page load in response to any request send to a production state n-tier app.
About the question of the 64Mb memory limit, i just can't understand what kind of n-tier app request would need to use such an among of RAM ?!! Any explainations about such kind of needs in the Rodeo Env. would probably help us to purpose alternative ways to go... I builded lots of PHP3/4/5 (+ Rev) n-tiers apps over the 15 last years and my httpd + php.ini configs went always configured to limit the requests timout in betwin 30-60 seconds and the among of RAM allowed to each PHP request to 2-4 Mb. Hope this can help. Best, Pierre Le 2 août 2010 à 16:29, Richard Gaskin a écrit : > That said, 30 seconds is a LONG time on a server. In Internet time, it's > close to "forever". Add normal network latency and browser rendering time to > that and you've got some serious user expectation issues. > > What server-side process could need that much time, and how many users will > wait for it? -- Pierre Sahores mobile : (33) 6 03 95 77 70 www.woooooooords.com www.sahores-conseil.com _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
