Andrea Suisani
2014-04-08 12:34:56 UTC
Hi all,
this is my first post to the list, I just wanna to say sorry in advance
if it's not the proper place where to ask about performances related question.
I've been assigned with a task that among other things include
the setup and tuning of limesurvey server.
This instance of limesurvey should have to deal with quite an heavy load so
I'm experimenting with lime survey tuning techniques.
So far on my test workstation I've been able to reach a peak of
20 req/s with an avg time of ~250ms. The machine is a quad core
box (i5-760) with 8 GB of RAM.
This is the pieces the define my stack:
- Limesurvey version is 2.05+ (140404)
- nginx 1.5.12 as webserver,
- php fast process manager as interpreter (communicate to nginx via unix socket)
- postgresql 9.3 as db.
I've installed APC cahing php opcode. On the DB
side I'm also using pgpoolII as server side query cache and
connections pooler.
In the limesurvey db settings I've enabled the cache
for the sql schema (schemaCachingDuration' => '3600').
I'm testing the performance using the apache ab tool, e.g. this
is the command I'm currently used that is giving me the perf of
20 req/s:
ab -n 1000 -c 5 http://192.168.1.50/997865/lang-en
I know that I'm only testing the load of the first page of the survey,
but for now it's enough.
I've a few questions for the community:
- is testing with ab a good way to measure performance?
- are the performance that I'm getting good enough / on par with your experiences?
- is there any better way to test limesurvey performance in a automated way?
- are there any other things to be done in orther to increase performances?
Thanks in advance.
Andrea
this is my first post to the list, I just wanna to say sorry in advance
if it's not the proper place where to ask about performances related question.
I've been assigned with a task that among other things include
the setup and tuning of limesurvey server.
This instance of limesurvey should have to deal with quite an heavy load so
I'm experimenting with lime survey tuning techniques.
So far on my test workstation I've been able to reach a peak of
20 req/s with an avg time of ~250ms. The machine is a quad core
box (i5-760) with 8 GB of RAM.
This is the pieces the define my stack:
- Limesurvey version is 2.05+ (140404)
- nginx 1.5.12 as webserver,
- php fast process manager as interpreter (communicate to nginx via unix socket)
- postgresql 9.3 as db.
I've installed APC cahing php opcode. On the DB
side I'm also using pgpoolII as server side query cache and
connections pooler.
In the limesurvey db settings I've enabled the cache
for the sql schema (schemaCachingDuration' => '3600').
I'm testing the performance using the apache ab tool, e.g. this
is the command I'm currently used that is giving me the perf of
20 req/s:
ab -n 1000 -c 5 http://192.168.1.50/997865/lang-en
I know that I'm only testing the load of the first page of the survey,
but for now it's enough.
I've a few questions for the community:
- is testing with ab a good way to measure performance?
- are the performance that I'm getting good enough / on par with your experiences?
- is there any better way to test limesurvey performance in a automated way?
- are there any other things to be done in orther to increase performances?
Thanks in advance.
Andrea