Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

low performance #86

Open
fazliddin opened this issue Dec 10, 2014 · 5 comments
Open

low performance #86

fazliddin opened this issue Dec 10, 2014 · 5 comments

Comments

@fazliddin
Copy link

My yii1 and yii2 fresh installs handle 150-220 request per second, but fresh install of boilerplate handles only 20-25. What is the reason?

@hijarian
Copy link
Contributor

Well, if you go as far as to profile newly-installed application templates, you can also look at the xdebug dump output with cachegrind and find the bottleneck yourself. :-| We did not do this, and your finding is interesting, by the way.

First idea that comes into my mind is that application templates which come with Yii 1.1 and Yii 2 assume your app is in production mode, and you need to enable debug mode manually. And in debug mode everything works slower. Try to re-run your profiling after putting an empty file named PRODUCTION_MODE in root of the codebase. Look at the check_prod_mode.php script for details. YiiBoilerplate assumes that you in debug mode by default, and you need to enable production mode manually. This is by design, because you have production mode on just a single deploy machine and almost always need the debug mode in all other cases.

@fazliddin
Copy link
Author

So, profiling showed that bottleneck was in using CDbHttpSession for session, as you can see below
dbsession
When I commented session part, performance increased for 2.5 times, that is 50 requests per second, here is profile
screenshot from 2014-12-13 23 09 11
But it is still slower where fresh yii1 which handles 150 r. p.s. As you see in second profile bottleneck is in CMap::mergeArray, YiiBase::import and YiiBase::autoload. It is because YiiBoilerplate uses very expensive method mergeArray for complex config files.

Actually I did not think that using database for session degrades performance.

@hijarian
Copy link
Contributor

Whoa, such a slow updates. Actually, database can be the botteneck if establishing connection to it is costly or it runs on a slow disk. Probably enabling DB caching will help, but I am not sure in this case, because most of the time were spent in UPDATE query.

@hijarian
Copy link
Contributor

Can you please provide the same profile charts for the fresh Yii 1.1 installation?

I certainly could not anticipate that combining arrays in PHP can be so costly as to decrease performance threefold.

@fazliddin
Copy link
Author

screenshot from 2014-12-18 00 27 14

my test is simple

ab -n 10 -c 2 http://yii-boilerplate
result: 90 req p.s.

ab -n 10 -c 2 http://yii-fresh
result: 150 req p.s.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants