On 10 Feb 2013, at 06:57, AmirBehzad Eslami behzad.esl...@gmail.com wrote:
Stuart, thanks for your detailed response.
I find it unlikely that Apache is your bottleneck,
especially with a service involving MySQL.
How have you come to this conclusion?
Apache is the entry-point to our
Bastien Koert
On 2013-02-09, at 11:42 AM, AmirBehzad Eslami behzad.esl...@gmail.com wrote:
Dear list,
We're a developing a PHP-driven web service with a RESTful API,
and we have a dedicated Linux server for that with 6GB of RAM.
Since this service will be used by many clients in a
Bastein,
Response is unique per request, and not cachable. The app
fetches records from MySQL (say, templates), performs a
process on them, and returns the generated output as JSON.
We were thinking to use Redis to reduce queries against
MySQL, but still Apache will remain as our bottleneck.
On 9 Feb 2013, at 16:42, AmirBehzad Eslami behzad.esl...@gmail.com wrote:
We're a developing a PHP-driven web service with a RESTful API,
and we have a dedicated Linux server for that with 6GB of RAM.
Since this service will be used by many clients in a concurrent
manner, we'll face with a
On Sat, Feb 9, 2013 at 12:21 PM, Stuart Dallas stu...@3ft9.com wrote:
On 9 Feb 2013, at 16:42, AmirBehzad Eslami behzad.esl...@gmail.com wrote:
We're a developing a PHP-driven web service with a RESTful API,
and we have a dedicated Linux server for that with 6GB of RAM.
I would personally
Stuart, thanks for your detailed response.
I find it unlikely that Apache is your bottleneck,
especially with a service involving MySQL.
How have you come to this conclusion?
Apache is the entry-point to our service, and I did a
benchmark with AB to see how it can handle concurrent
requests
6 matches
Mail list logo
