We have just upgraded from 3.18 to 3.22 and I thought people would be interesting in seeing the before and after graphs.
This is the DB load over the last 24 hours.
[attachment=417:cacti-load.jpg]
You can see a big dip in load (close to 50%).
The load on the App server is unchanged (even using memcached for sessions).
As far as responsiveness goes, the plain upgrade (no memcached) dramatically improved admin performance.
Post adding memcached also seems to improve admin speed.
The front end seems to be faster, but it is hard to say as we have put in place other non-matrix measures already.
cheers,
Richard
cacti-load.jpg (24.5 KB)
Hi,
[quote]
We have just upgraded from 3.18 to 3.22 and I thought people would be interesting in seeing the before and after graphs.
This is the DB load over the last 24 hours.
[attachment=417:cacti-load.jpg]
You can see a big dip in load (close to 50%).
The load on the App server is unchanged (even using memcached for sessions).
As far as responsiveness goes, the plain upgrade (no memcached) dramatically improved admin performance.
Post adding memcached also seems to improve admin speed.
The front end seems to be faster, but it is hard to say as we have put in place other non-matrix measures already.
cheers,
Richard
[/quote]
Awesome 
Note that not everyone will get a huge improvement like this (it'll be based on how your site is structured) but hopefully you'll see some improvements in each major upgrade.
[quote]
Awesome Note that not everyone will get a huge improvement like this (it'll be based on how your site is structured) but hopefully you'll see some improvements in each major upgrade.
[/quote]
True. We have a lot of asset listings, nested asset listing, and site wide stuff going on.
[quote]
True. We have a lot of asset listings, nested asset listing, and site wide stuff going on.
[/quote]
It's still very interesting to see the improvements, thanks for sharing
Our upgrade was worth it. Speed and load time improved a lot. We use to have problem where database are hogging the CPU resource, but the problem seems to gone away after we upgrade to 3.2.
Im not sure if the older version behave the same way, but in the new version queries seems to be serialized. Instead of having few 1 heavy queries, I notice that the 3.2 generate lots of small queries.
Our main page generate 1329 small queries to load un-cached page. This architecture provide good and bad points. The good point is that you will see huge drop in load average on the database server and you will not see much activity in there ( because the queries runs very fast).
The bad : This architecture suffer from ripple effect where 1 slow transaction will cause subsequent transaction seems slower.
Just like a traffic jam : [image removed]
Luckily the cache helps a lot …
It's good your getting results :P~