Textpattern CMS support forum

You are not logged in. Register | Login | Help

#1 2018-09-14 10:29:12

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 8,341
Website

Snappy 4.7

I’m aware this sounds like blowing our own trumpet, but I just upgraded the site I’m working on for a client from 4.6.2 to 4.7.1. No other server changes whatsoever, a simple update. Server’s running on the lowest Digital Ocean droplet, with Apache, Percona and PHP 7.0.something as I haven’t updated to the latest yet.

Been working on the 4.6.2 site for a few days, modifying Pages and Forms and clicking articles to test things, and navigating the admin side yahde yahde. Was impressed with how it behaved. But wow, after the upgrade everything just feels so much more responsive. Like, a huge step up.

Sure, there were a few MB of logs which have now been zapped on update so that’ll be having a fair impact on public site performance, but overall the entire experience feels super clean and super fast on both public site and admin side.

I’m majorly proud of our success at managing to pack this many new features into Textpattern and not only keep its nimble spirit alive but also to make it more efficient and a joy to work with.

Hats off to everyone who has made 4.7 what it is. Looking forward to our next milestone.


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#2 2018-09-14 12:49:13

philwareham
Core designer
From: Farnham, Surrey, UK
Registered: 2009-06-11
Posts: 3,049
Website

Re: Snappy 4.7

Yep, here’s some real-world speed testing of our homepage (which is fairly heavy due to media within) and a less-heavy (and fairly standard) blog article which bears out your own experiences:

Homepage

Blog article

And just for fun, homepages of some other CMSes as a comparison. Not too scientific, but you’d assume each was running on pretty optimal code and hardware. In order of performance. Oh dear, Drupal, oh dear (so glad I don’t have to use that CMS in my day job any more).

Offline

#3 2018-09-14 12:53:35

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 6,768
Website

Re: Snappy 4.7

Yummy! Phil, where did you do those tests?


Yiannis
——————————
neme.org | hblack.net | LABS | State Machines | NeMe @ github

Offline

#4 2018-09-14 12:58:29

philwareham
Core designer
From: Farnham, Surrey, UK
Registered: 2009-06-11
Posts: 3,049
Website

Re: Snappy 4.7

colak wrote #314021:

Yummy! Phil, where did you do those tests?

Pingdom Tools

Offline

#5 2018-09-14 22:08:17

gaekwad
Member
From: People's Republic of Cornwall
Registered: 2005-11-19
Posts: 2,326

Re: Snappy 4.7

philwareham wrote #314020:

Yep, here’s some real-world speed testing of our homepage (which is fairly heavy due to media within) and a less-heavy (and fairly standard) blog article which bears out your own experiences:

That’s very pleasing.

Offline

#6 2018-09-15 09:19:15

zero
Member
From: Lancashire
Registered: 2004-04-19
Posts: 1,137
Website

Re: Snappy 4.7

Bloke wrote #314018:

I’m majorly proud of our success at managing to pack this many new features into Textpattern and not only keep its nimble spirit alive but also to make it more efficient and a joy to work with.

Hats off to everyone who has made 4.7 what it is. Looking forward to our next milestone.

Well done Stef and all you Developers and contributors. It’s a beautiful thing you’re doing.


TXPQ Examples and discussion of Textpattern CMS quality.
Safe Reiki Harmless natural healing.

Offline

#7 2018-09-15 09:28:45

etc
Developer
Registered: 2010-11-11
Posts: 2,778
Website

Re: Snappy 4.7

Looks like the slower the better, popularity-wise.


etc_[ query | search | pagination | date | tree | cache ]

Offline

#8 2018-09-16 00:18:16

bici
Member
From: vancouver
Registered: 2004-02-24
Posts: 1,275
Website

Re: Snappy 4.7

philwareham wrote #314023:

Pingdom Tools

cool. so i decided to test my site.

Report says:
The following cacheable resources have a short freshness lifetime. Specify an expiration at least one week in the future for the following resources:

anyone have any idea how to do what is suggested?


…. texted postive

Offline

#9 2018-09-16 05:18:14

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 6,768
Website

Re: Snappy 4.7

bici wrote #314058:

cool. so i decided to test my site.

Report says:
The following cacheable resources have a short freshness lifetime. Specify an expiration at least one week in the future for the following resources:

anyone have any idea how to do what is suggested?

Add in your htaccess


<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg "access plus 1 year"
ExpiresByType image/jpeg "access plus 1 year"
ExpiresByType image/gif "access plus 1 year"
ExpiresByType image/png "access plus 1 year"
ExpiresByType text/css "access plus 15 days"
ExpiresByType text/html "access plus 10 seconds"
ExpiresByType application/pdf "access plus 1 month"
ExpiresByType application/javascript "access plus 1 month"
ExpiresByType application/x-javascript "access plus 1 month"
ExpiresByType text/javascript "access plus 1 month"
ExpiresByType application/x-shockwave-flash "access plus 1 month"
ExpiresByType image/x-icon "access plus 1 month"
ExpiresByType application/atom+xml "access plus 1 hour"
ExpiresByType application/rss+xml "access plus 1 hour"
ExpiresDefault "access plus 1 month"
</IfModule>

Yiannis
——————————
neme.org | hblack.net | LABS | State Machines | NeMe @ github

Offline

#10 2018-09-16 08:32:47

jakob
Moderator
From: Germany
Registered: 2005-01-20
Posts: 3,031
Website

Re: Snappy 4.7

bici wrote #314058:

The following cacheable resources have a short freshness lifetime. Specify an expiration at least one week in the future for the following resources:

anyone have any idea how to do what is suggested?

Check what’s listed under “following resources”. You can optimise that for data served from your own site but if they’re external services, I don’t think you can (correct me please someone if I’m wrong).
I get that message when using typekit and the best you can do there (I think) is extend the caching period in the typekit kit settings.

colak wrote #314059:

Add in your htaccess

There’s also a quite comprehensive list from here downwards in the HTML5 Boilerplate htaccess file.


TXP Builders – finely-crafted code, design and txp

Offline

Board footer

Powered by FluxBB