kick-starting the work on ngx_pagespeed & design discussions

[Ilya Grigorik]

Hello world!

There is a lot to cover and to discuss, but let's start at the beginning. Namely, here are the project goals we've identified so far:

• ngx_pagespeed should have feature-parity with mod_pagespeed
  
• the only features it makes sense to omit are the ones that are very specific to Apache, e.g. dynamic configuration via .htaccess
  
• The design of our system should be such that all features available in mod_pagespeed automatically apply to ngx_pagespeed, rather than porting over features individually
  
• ngx_pagespeed should be be easy-to-adopt
  

We would love to get a prototype up and running as soon as possible, and to that end, we've already kicked off some experimental branches on GitHub:

https://github.com/pagespeed/ngx_pagespeed - this will be the main repository for the code, issue tracking, and so forth. 

In case you are wondering about CLA's and all that stuff for contributing code: none required, as long as you are not modifying the core PageSpeed Optimization Libraries (PSOL), and if that's the case, then it's a simple "click-to-accept" process. 

We do have a design doc (work in progress!), which we would love to get everyone's input and feedback on:

https://docs.google.com/document/d/1SwoxivAO7fxUhKHU6ks5BEwc6FjE73kvYzva2aceVrc/edit

There are definitely a lot of gaps in the doc above, which I'm hoping we can fill in and discuss on this mailing list in the coming days, weeks, and months.

Finally, as a quick summary of our progress to date... We have Josh Marantz, Jeff Kaufman and myself from the Google side who have been looking into the nginx port. We've also had good discussions and feedback from the nginx team on the module, as well as a number of other individual contributors: Ben Noordhuis, Otto van der Schaaf, and Piotr Sikora. 

Kudos to everyone who has helped us bootstrap the project so far, and more importantly... Looking forward to working with everyone on ngx_pagespeed from here on! :-)

Ilya

[yaoweibin]

Hi,

As a novice of pagespeed, I'm curious about the apr_memcache is used for what in mod_pagespeed.

Thanks.

Ilya Grigorik於 2012年10月12日星期五UTC+8上午6時59分25秒寫道：

[Joshua Marantz]

apr_memcache is used to remember resource (css / images / js) optimizations in mod_pagespeed.  The current released version doesn't support that, but it is available in trunk and will be released in the next beta.  Progress is tracked here: http://code.google.com/p/modpagespeed/issues/detail?id=475.

We will want a similar solution in nginx.

-Josh

--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
Visit this group at http://groups.google.com/group/ngx-pagespeed-discuss?hl=en.
 
 

[Weibin Yao]

Thanks. I'll read this feature tomorrow.

The srcache module can store and fetch the page with key value database.
https://github.com/agentzh/srcache-nginx-module . This module uses many subrequests which can issue requests to backend servers.

On 2012-10-14 21:21, Joshua Marantz wrote:

apr_memcache is used to remember resource (css / images / js) optimizations in mod_pagespeed.  The current released version doesn't support that, but it is available in trunk and will be released in the next beta.  Progress is tracked here: http://code.google.com/p/modpagespeed/issues/detail?id=475.

We will want a similar solution in nginx.

-Josh

On Sun, Oct 14, 2012 at 2:52 AM, yaoweibin <yaow...@gmail.com> wrote:

Hi,

As a novice of pagespeed, I'm curious about the apr_memcache is used for what in mod_pagespeed.

Thanks.

Ilya Grigorik嚙踝蕭 2012嚙羯10嚙踝蕭12嚙踝蕭P嚙踝蕭嚙踝蕭UTC+8嚙磕嚙踝蕭6嚙踝蕭59嚙踝蕭25嚙踝蕭g嚙瘩嚙瘦

Hello world!

There is a lot to cover and to discuss, but let's start at the beginning. Namely, here are the project goals we've identified so far:

• ngx_pagespeed should have feature-parity with mod_pagespeed
  
• the only features it makes sense to omit are the ones that are very specific to Apache, e.g. dynamic configuration via .htaccess
  
• The design of our system should be such that all features available in mod_pagespeed automatically apply to ngx_pagespeed, rather than porting over features individually
  
• ngx_pagespeed should be be easy-to-adopt
  

We would love to get a prototype up and running as soon as possible, and to that end, we've already kicked off some experimental branches on GitHub:

https://github.com/pagespeed/ngx_pagespeed - this will be the main repository for the code, issue tracking, and so forth. 

In case you are wondering about CLA's and all that stuff for contributing code: none required, as long as you are not modifying the core PageSpeed Optimization Libraries (PSOL), and if that's the case, then it's a simple "click-to-accept" process. 

We do have a design doc (work in progress!), which we would love to get everyone's input and feedback on:

https://docs.google.com/document/d/1SwoxivAO7fxUhKHU6ks5BEwc6FjE73kvYzva2aceVrc/edit

There are definitely a lot of gaps in the doc above, which I'm hoping we can fill in and discuss on this mailing list in the coming days, weeks, and months.

Finally, as a quick summary of our progress to date... We have Josh Marantz, Jeff Kaufman and myself from the Google side who have been looking into the nginx port. We've also had good discussions and feedback from the nginx team on the module, as well as a number of other individual contributors: Ben Noordhuis, Otto van der Schaaf, and Piotr Sikora. 

Kudos to everyone who has helped us bootstrap the project so far, and more importantly... Looking forward to working with everyone on ngx_pagespeed from here on! :-)

Ilya

--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
Visit this group at http://groups.google.com/group/ngx-pagespeed-discuss?hl=en.
 
 

--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
Visit this group at http://groups.google.com/group/ngx-pagespeed-discuss?hl=en.
 
 

-- 
Thanks,
-Weibin Yao