You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pagespeed.apache.org by GitBox <gi...@apache.org> on 2020/01/30 22:58:23 UTC
[GitHub] [incubator-pagespeed-ngx] mr-observer opened a new issue #1678:
What about the PageSpeed module development?
mr-observer opened a new issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678
I see only one commit past year nad it was just a fix... This project is "finished" and we have to abandon it in the future? Just because standards of the web changing a bit fast and it has no support?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] jmarantz commented on issue #1678: What
about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
jmarantz commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-580504301
The github repo is open and we would welcome PRs to improve the product. Are you interested?
Agreed there is a ton to do.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] mr-observer commented on issue #1678:
What about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
mr-observer commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-580515779
Glad to hear that work in progress. What about moving downstream caching from "experimental" to "prod-ready" at least with the most popular Varnish HTTP Accelerator?
I know that you probably will tell me that it's ready, but we have some fundamental problems with that in production.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] pmjcreations commented on issue #1678:
What about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
pmjcreations commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-591935386
> We're working to produce an apache incubator release for mod_pagespeed; updating ngx_pagespeed to leverage that new version and ship a new release based on that will be low hanging fruit.
I see [v1.14.36.1](https://github.com/apache/incubator-pagespeed-mod/releases/tag/v1.14.36.1) released 17 days ago.
@oschaaf, if this is a stable release, can we expect a new release for Nginx sometimes soon?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] mr-observer commented on issue #1678:
What about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
mr-observer commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-581085298
> Well jmarantz suggested OptimizeForBandwidth, which I think is easy to do.
I tried OptimizeForBandwidth, but it behaves the same way in this case.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] mr-observer commented on issue #1678:
What about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
mr-observer commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-580538715
It looks like a problem in the way PageSpeed purging the content from Varnish.
At the start, its behavior is like described on the image in documentation: https://www.modpagespeed.com/doc/downstream-caching
But next, it's randomly purging (after 5 or more minutes of serving cached content) the cache from Varnish and we getting cache misses when TTL is set to 24h.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1678: What
about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
oschaaf commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-580511643
We're working to produce an apache incubator release for mod_pagespeed; updating ngx_pagespeed to leverage that new version and ship a new release based on that will be low hanging fruit.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1678: What
about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
oschaaf commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-580520348
As far as I know no one is planning to mark that as production ready at this time, mostly because it’s not clear how many people are running that in production. What kind of trouble did you run in to in production? If it’s fixable in VCL then arguably it might be a documentation fix or extension, which would be very welcome! :)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1678: What
about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
oschaaf commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-580696497
I think cacheability of the html is restricted to the recursive minimum of
all resources included in the page, by nature of how the module works (if
resources urls are rewritten to .pagespeed. variants). 404s will count as 5
minutes by default, so these could degrade html cacheability, also when
included indirectly via css.
On Fri, 31 Jan 2020 at 02:22, observer.name <no...@github.com>
wrote:
> It looks like a problem in the way PageSpeed purging the content from
> Varnish.
> At the start, its behavior is like described on the image in
> documentation: https://www.modpagespeed.com/doc/downstream-caching
>
> But next, it's randomly purging (after 5 or more minutes of serving cached
> content) the cache from Varnish and we getting cache misses when TTL is set
> to 24h.
>
> —
> You are receiving this because you commented.
>
>
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/incubator-pagespeed-ngx/issues/1678?email_source=notifications&email_token=AARCYRFB4RMTWZEWYOVGCALRAN4N7A5CNFSM4KN6OD6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKNFCWY#issuecomment-580538715>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AARCYRAJY5B5PFBVFF6OTF3RAN4N7ANCNFSM4KN6OD6A>
> .
>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] mr-observer edited a comment on issue
#1678: What about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
mr-observer edited a comment on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-581085306
> Well jmarantz suggested OptimizeForBandwidth, which I think is easy to do.
I tried OptimizeForBandwidth, but it behaves the same way in this case.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] mr-observer commented on issue #1678:
What about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
mr-observer commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-580509584
I thought it is supported by Google and isn't by the community.
Looks like I don't have enough skill in C to improve this product, but I can tell the direction in which it may go in the future just because I tested a lot of things using it.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] mr-observer commented on issue #1678:
What about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
mr-observer commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-581085306
> > Well jmarantz suggested OptimizeForBandwidth, which I think is easy to do.
I tried OptimizeForBandwidth, but it behaves the same way in this case.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] mr-observer commented on issue #1678:
What about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
mr-observer commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-581081252
> I think cacheability of the html is restricted to the recursive minimum of all resources included in the page, by nature of how the module works (if resources urls are rewritten to .pagespeed. variants). 404s will count as 5 minutes by default, so these could degrade html cacheability, also when included indirectly via css.
Can we workaround this in some way?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1678: What
about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
oschaaf commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-591936422
1.14.36.1 got tagged, but has not been released yet, even though it did get approval by the incubator PMC:
While finalizing the release steps, a blocking issue was observed in the scripts that create .deb/.rpm packages. I'm working on that.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] jmarantz commented on issue #1678: What
about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
jmarantz commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-580725757
One thought -- can't remember what the code state is -- if we are using OptimizeForBandwidth for assets, we don't need to include them in the MIN for computing the HTML cacheability, whether they are 404 or successful.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] mr-observer removed a comment on issue
#1678: What about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
mr-observer removed a comment on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-581085298
> Well jmarantz suggested OptimizeForBandwidth, which I think is easy to do.
I tried OptimizeForBandwidth, but it behaves the same way in this case.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] mr-observer edited a comment on issue
#1678: What about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
mr-observer edited a comment on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-580509584
I thought it is supported by Google and isn't by the community.
Looks like I don't have enough skill in C to improve this product, but I can tell the direction in which it may go in the future just because I tested a lot of things using it as web developer/admin.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] mr-observer edited a comment on issue
#1678: What about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
mr-observer edited a comment on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-580515779
Glad to hear that work in progress. What about moving downstream caching from "experimental" to "prod-ready" at least with the most popular Varnish HTTP Accelerator?
You probably will tell me that it's ready and documented, but we have some fundamental problems with that in production.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [incubator-pagespeed-ngx] oschaaf commented on issue #1678: What
about the PageSpeed module development?
Posted by GitBox <gi...@apache.org>.
oschaaf commented on issue #1678: What about the PageSpeed module development?
URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1678#issuecomment-581083300
Well jmarantz suggested OptimizeForBandwidth, which I think is easy to do.
Or possibly one could add some nginx configuration to transform resource
response headers to override origin cache TTL before pagespeed gets to see
them, if .pagespeed. rewriting is a must. Plus configure pagespeed to cache
404s longer then 5 minutes.
Otto
On Sun, 2 Feb 2020 at 00:42, observer.name <no...@github.com> wrote:
> I think cacheability of the html is restricted to the recursive minimum of
> all resources included in the page, by nature of how the module works (if
> resources urls are rewritten to .pagespeed. variants). 404s will count as 5
> minutes by default, so these could degrade html cacheability, also when
> included indirectly via css.
>
> Can we workaround this in some way?
>
> —
> You are receiving this because you commented.
>
>
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/incubator-pagespeed-ngx/issues/1678?email_source=notifications&email_token=AARCYRCJ3OXYFMPFHXTLCSDRAYCFBA5CNFSM4KN6OD6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKRJRJA#issuecomment-581081252>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AARCYREHLLEZURJTRWDUM4LRAYCFBANCNFSM4KN6OD6A>
> .
>
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services