If you really do need 10k simultaneous calls, you will be having a
cluster of servers :-)
So the efficiency of a single one isn't as important.
And a better organised set of files in the service will help maintenance
and bug fixing.
Tom
On 11/04/17 15:33, Jeffry Houser wrote:
It is not really a Flex question, so I generally agree.
My expectation is that PHP will be able to handle multiple threads /
concurrent requests [just like most other server side software I've
used]. At certain traffic limitations you may need to use a more
powerful server, or even multiple servers to prevent things from
getting overloaded.
It seems unlikely to me that you'll have 10K users accessing the same
service simultaneously, but it depends on the app your user base and
the success of the venture.
On 4/11/2017 6:55 AM, Fréderic Cox wrote:
I think this is a question that is better suited for stackoverflow.
On Tue, Apr 11, 2017 at 3:21 AM, bilbosax <[email protected]>
wrote:
This is just a little theoretical question I have wondered about, so I
thought I would ask it here. I am writing an app that I hope will
have at
least 10k users daily. When you set up your services, you can
technically
put them all in a single PHP file if you want to, or spread them out
across
several files that are more specific, however you want to do it.
But I am
curious, if I have 10k users trying to access a single PHP file
instead of
having the workload spread across several PHP files, will this cause a
bottleneck, and will I lose efficiency.
I have no idea how PHP handles multiple users. Does anybody know if
the
workload will be handled more efficiently if the PHP services are
spread
across multiple files rather than one big one?
Thanks for any insight.
--
View this message in context: http://apache-flex-users.
2333346.n4.nabble.com/PHP-Service-Efficiency-tp15015.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
