Performance

ghristov

Hallo EPESI team,

Somehow I am not able to match the amazing performance of EPESI on the demo page. For instance both on development server (my laptop with Windows) and the production machine (under Linux) the Companies and Contacts pages render in about 1.8s each which is visibly slower than the 295ms on your demo server.

Below is the output of module times and SQL times. I am caching Common files on the production machine:

I will appreciate some hints in direction of improving performance.

Best regards,
Georgi

ajb

After your post I've decided to test my results.
I've got ~0.8s for contacts view on my localhost - i7, 8GB RAM, SSD drive, without optimizations
And ~0.3s on our hosting/demo.

We use RunAbove and it's really fast.
FastCGI, memcache for session and different machine for sql server.

I've tried some optimizations and there is some part of code that causes huge slowdown of processing callbacks. Now I've reduced demo.epesibim.com time (contacts browse) to ~0.22. With one simple change.
On my localhost I've got now (with more tweaks) ~0.4s
On our installation those changes reduced time form ~0.6s to ~0.3s. https://github.com/Telaxus/EPESI/commit ... f0e88b37c6

However notice that for my localhost installation and our installation those times compare with just one commit. On our demo we've got the latest release which could be faster due to some modifications made since last release - I haven't tested that.

To sum up:
1. RunAbove is really fast - I have no idea how they do this.
2. I bet that there is still some place for code optimizations or cleanup.

Now some ideas to improve performance
1. Try to use APC or any other PHP accelerator
2. Try different types of session storage - memcache, files, database. For my localhost memcache is no faster than files (probably due to ssd drive).
3. Try to put database server on different machine that http server

Best regards,
Adam

ghristov

Hi Adam,

Thanks for detailed info. Actually I wanted to update to the dev version so we have the same feedback. I was running 1.6.3 till now due to some custom code I have to implement in each new Epesi version.
Anyway I do not have significant improvement with the dev version, was trying all types of sessions without any difference. Tried also APC - also cannot say there is noticeable improveent.
Meanwhile on my side the sql session types expires too often but I have not investigated that yet.

I started running Xdebug profiling to figure out the bottlenecks. There is nothing standing out dramatically but I will post whatever I come across here.
The first thing I noticed is that Utils_RecordBrowserCommon::user_settings() method slows down script execution especially if RB has many tabs as it checks the access for each tab every time. Maybe we should consider another way of organizing the settings for RB?

Will post further findings.

Best regards,
Georgi

ajb

I've found the same as you. It loads user settings in each RB related view - browse, view record, so I guess in 90% of requests. I'll try to do something about this.

ajb

I've decided to store default settings in user session, as they may differ for each user. https://github.com/Telaxus/EPESI/commit ... 27616424f9
It speeds up a little bit.

ghristov

I managed to compare the speed with a clean install with only default modules.
Same machine, same Apache - MySQL - PHP arrangement, EPESI dev version.

info : clean installation / production installation:
- opening Contacts : 310 ms / 1070 ms
- modules : 87 / 172
- RB recordsets : 14 / 74

It looks like performance is reversely proportional to the number of modules / recordsets installed.
Any idea how to reduce the influence of installed modules on performance?

regards,
georgi

ajb

I'll try to manage some time and run profiles against my cluttered dev install and clean dev install to compare them.

Epesi ENS | Epesi Academy | epesi.cloud PaaS | GitHub

Help Me! | Download from SourceForge