rvm_css (v1.2)

hcgtv · 2008-01-06 18:01:17

ruud wrote:

Bert, try benchmarking the difference between loading css.php and the static stylesheet.css file instead.

Let’s welcome JoeDog’s siege to the proceedings.

urls-cssphp.txt:

http://txpage.com/about/
http://txpage.com/textpattern/css.php?s=about
http://txpage.com/textpattern/txp_img/carver.gif
http://txpage.com/images/1.gif

siege -d1 -r10 -c25 -f /home/bert/urls-cssphp.txt

Transactions: 250 hits
Availability: 100.00 %
Elapsed time: 7.22 secs
Data transferred: 0.48 MB
Response time: 0.08 secs
Transaction rate: 34.63 trans/sec
Throughput: 0.07 MB/sec
Concurrency: 2.84
Successful transactions: 250
Failed transactions: 0
Longest transaction: 0.92
Shortest transaction: 0.00

urls-static.txt:

http://txpage.com/about/
http://txpage.com/_templates/default.css
http://txpage.com/textpattern/txp_img/carver.gif
http://txpage.com/images/1.gif

siege -d1 -r10 -c25 -f /home/bert/urls-static.txt

Transactions: 250 hits
Availability: 100.00 %
Elapsed time: 7.86 secs
Data transferred: 0.48 MB
Response time: 0.02 secs
Transaction rate: 31.81 trans/sec
Throughput: 0.06 MB/sec
Concurrency: 0.75
Successful transactions: 250
Failed transactions: 0
Longest transaction: 0.19
Shortest transaction: 0.00

The APC cached css.php wins against the static css file, go figure.

typeshige · 2008-01-06 18:12:07

I did the same thing but compared as rudd suggested:

My css file is 28k big.

Without:
Concurrency Level: 5
Time taken for tests: 12.173134 seconds
Complete requests: 100
Failed requests: 0
Write errors: 0
Total transferred: 2894400 bytes
HTML transferred: 2880400 bytes
Requests per second: 8.21 ¹ (mean)
Time per request: 608.657 [ms] (mean)
Time per request: 121.731 [ms] (mean, across all concurrent requests)
Transfer rate: 232.15 [Kbytes/sec] received

With:
Concurrency Level: 5
Time taken for tests: 2.338252 seconds
Complete requests: 100
Failed requests: 0
Write errors: 0
Total transferred: 2904100 bytes
HTML transferred: 2880400 bytes
Requests per second: 42.77 ¹ (mean)
Time per request: 116.913 [ms] (mean)
Time per request: 23.383 [ms] (mean, across all concurrent requests)
Transfer rate: 1212.87 [Kbytes/sec] received

This plugin is awesome! What else might be speeded up using this method? Would it make sense to have static pages and forms as well?

Last edited by typeshige (2008-01-06 18:13:39)

ruud · 2008-01-06 18:59:13

This is what I get, with a CSS file that’s 2.4kB

without: ab -c 5 -n 250 http://path/to/css.php
Requests per second: 10.46 ¹ (mean)

with: ab -c 5 -n 10000 http://path/to/static.css
Requests per second: 1026.68 ¹ (mean)

I used 10000 on the second one so the tests ran an near equal amount of time (otherwise the second test would be too inaccurate). This was tested by using “ab” on the same server that hosted the website to exclude network latencies and throughput issues.

Bert, I think you’re not measuring APC speed, but some kind of connection limitation on the webserver that hosts your website or simply the latency or throughput fluctuation between your webhost and the server where you’re running “ab” or “siege”.

typeshige, you can’t use this to speed up forms/pages in TXP, because those are combined with article data that is pulled from the database to form the website page that is sent to the visitor. The technique to speed up css files here really only works for page elements (as requested by the browser!) that can be stored entirely as a static file.

hcgtv · 2008-01-06 22:53:49

ruud wrote:

Bert, I think you’re not measuring APC speed, but some kind of connection limitation on the webserver that hosts your website or simply the latency or throughput fluctuation between your webhost and the server where you’re running “ab” or “siege”.

The tests were run on the same machine that runs the websites.

All I know is that with APC, the amount of requests my web server can handle was multiplied by a factor of 5. Which I think is what brings a site using css.php on par with a statically linked css file, at least that’s what all my tests have shown.

On a side note, the way you save off the CSS to a file could be extended to pages and forms. If you don’t mind, may I use some of your logic and add it to my templates plugin? I want to make the directory where the templates are stored an admin preference and I’d like to have archive capabilities with timestamped files, for backup purposes.

ruud · 2008-01-06 23:13:31

Bert, my plugins are released under GPLv2 or later license. Within the limits of that license, you’re free to re-use my code ;)

iblastoff · 2008-01-06 23:37:39

hcgtv wrote:

On a side note, the way you save off the CSS to a file could be extended to pages and forms. If you don’t mind, may I use some of your logic and add it to my templates plugin? I want to make the directory where the templates are stored an admin preference and I’d like to have archive capabilities with timestamped files, for backup purposes.

do you mean we could have ‘revisions’ of say..a css stylesheet?

for example in typolight CMS, whenever you save a stylesheet, a revision is made so you can easily revert a change:

Last edited by iblastoff (2008-01-06 23:43:01)

hcgtv · 2008-01-06 23:49:15

ruud, thanks.

steve, yes, and you’ll also have revisions of your pages and forms.

iblastoff · 2008-01-06 23:59:31

hcgtv wrote:

steve, yes, and you’ll also have revisions of your pages and forms.

bert that would be beautious!!!

Last edited by iblastoff (2008-01-06 23:59:46)

thebombsite · 2008-01-07 00:21:15

Whoa – go for it Bert. :)

guiguibonbon · 2008-01-12 04:26:07

Oh, lord! At last!

I have been praying for this. I really have.

FireFusion · 2008-01-12 11:09:41

hcgtv wrote:

steve, yes, and you’ll also have revisions of your pages and forms.

Woo! Let me know when it’s released. I’ve really been longing for this feature.

Last edited by FireFusion (2008-01-12 11:10:04)

NickML · 2008-01-12 20:39:39

Impressive stuff, Ruud – thank you.

If you were considering a future feature – one might be an option on the CSS edit window, next to “save”, to strip out comments and whitespace in the static version (but it still remains annotated in the editable version).

The reason I think it would need to be an option is that I’ve seen otherwise well-behaved stylesheets with maybe just a missing semi-colon suddenly break when stripping out comments and whitespace.

~Nick

creativesplash · 2008-01-12 22:55:59

I’ve implemented this in all the txp based sites. This really speeds up things! Neat job!

aswihart · 2008-01-13 19:11:34

This plugin seems to be a great complement to asy_jpcache. Do you all use that one too? Thanks a lot Ruud!

candyman · 2008-02-01 01:12:08

I have a problem with, I think, file permission.
The directory is created (at the same level of images one), named lovercase css and the path is correct (in advanced preferences I have this: Style directory: css).
Anyway, even if I choose a style file and save, nothing appears in the css directory.

What should I control?

Thnks in advance.

EDIT: solved

Last edited by candyman (2008-02-01 08:28:59)

Textpattern CMS

Textpattern CMS support forum

#31 2008-01-06 18:01:17

Re: rvm_css (v1.2)

#32 2008-01-06 18:12:07

Re: rvm_css (v1.2)

#33 2008-01-06 18:59:13

Re: rvm_css (v1.2)

#34 2008-01-06 22:53:49

Re: rvm_css (v1.2)

#35 2008-01-06 23:13:31

Re: rvm_css (v1.2)

#36 2008-01-06 23:37:39

Re: rvm_css (v1.2)

#37 2008-01-06 23:49:15

Re: rvm_css (v1.2)

#38 2008-01-06 23:59:31

Re: rvm_css (v1.2)

#39 2008-01-07 00:21:15

Re: rvm_css (v1.2)

#40 2008-01-12 04:26:07

Re: rvm_css (v1.2)

#41 2008-01-12 11:09:41

Re: rvm_css (v1.2)

#42 2008-01-12 20:39:39

Re: rvm_css (v1.2)

#43 2008-01-12 22:55:59

Re: rvm_css (v1.2)

#44 2008-01-13 19:11:34

Re: rvm_css (v1.2)

#45 2008-02-01 01:12:08

Re: rvm_css (v1.2)

Board footer