Is there a minimum requirement for apache 2.4 to run these tests?
I have tried on different machines with different configurations with the
same outcome.
Please advise.
Thanks,
RS
On Fri, Sep 23, 2016 at 1:14 AM, Rashmi Srinivasan <
rashmisrinivasan2...@gmail.com> wrote:
> Hi,
> Thanks for
Hi,
Do you feel this is the issue with some configuration or would this be an
issue with apache itself.
Has anybody encountered a performance issue of this kind.
Please comment
Thanks,
RS
On Fri, Sep 23, 2016 at 1:43 PM, Rashmi Srinivasan <
rashmisrinivasan2...@gmail.com> wrote:
> Is there a
Are you testing from de same host that runs httpd?
Could you paste paste the output of ulimit -a , ie:
[apache@--- ~]$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks,
Hi All,
We have installed apache 2.4.12 package on AIX 7 64 bit. We are unable to make
use of SSL cipher options in the configuration.
Module mod_ssl is pointing to openssl 0.9.8 version. (sudo strings
/usr/IBMAHS/modules/mod_ssl.so | grep -i openssl)
/usr/IBMAHS/bin/apachectl -version
Server
I think your problem is not Apache, but your OS.
I think Apache 2.2 and 4.4 uses diferent mpm mode (my memory is poor).
I think you OS is limiting the number of Opens Files that can Manage.
(safety reasons)
Please, can you print you ulimit output, as I advise on a previous mail?
Thanks.
At 12:18 AM 9/24/2016 +0530, Rashmi Srinivasan wrote:
Hi,
This is the output of ulimit -aÂ
[snip]
max user processes        (-u) 1024
Pure guesswork, but this looks low -- on a 32bit system, try 2^15; on
64bits, 2^16 ... or more ...
P.
virtual memory      (kbytes,
Thanks
I will check this.
I have another concern related to performance.
on RHEL machine, running ab for 2 requests with 100 concurrent requests
takes almost 46 seconds, while this was taking just 2 seconds in 2.2
Please can you tell if this is the case and how can this be improved?
Thanks
Hi,
This is the output of ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 15944
max locked memory (kbytes, -l) 64
max