Skip to content

Conversation

@MorrisJobke
Copy link
Member

While looking into our apps.nextcloud.com server I realized that the requests are not compressed. Even if the server supports it the clients don't request it. Thus the server sends out 5 MB instead of the compressed 2 MB. This and the raised cache time of 60 instead of 5 minutes should reduce the overall load of the app store server quite a lot.

As those are quite small changes I would backport them down to stable16.

@MorrisJobke MorrisJobke added bug 3. to review Waiting for reviews labels May 19, 2020
@MorrisJobke MorrisJobke added this to the Nextcloud 20 milestone May 19, 2020
@MorrisJobke
Copy link
Member Author

/backport to stable19

@MorrisJobke
Copy link
Member Author

/backport to stable18

@MorrisJobke
Copy link
Member Author

/backport to stable17

@MorrisJobke
Copy link
Member Author

/backport to stable16

Copy link
Contributor

@kesselb kesselb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@rullzer
Copy link
Member

rullzer commented May 20, 2020

The tests say no

In test it reduced the transfered data from 5 MB to 2 MB. This should reduce the load on the appstore significantly.

Signed-off-by: Morris Jobke <[email protected]>
@MorrisJobke MorrisJobke force-pushed the bug/noid/caching-and-gzipping-of-appstore-requests branch from c64fd31 to 6ffde12 Compare May 20, 2020 07:51
@MorrisJobke
Copy link
Member Author

The tests say no

I fixed them :) Wasn't as easy as a lot of logic was hidden in getTime values.

@ChristophWurst
Copy link
Member

I wonder if this should be generally the default for our http client. Would there be any downside to that?

@rullzer
Copy link
Member

rullzer commented May 20, 2020

I wonder if this should be generally the default for our http client. Would there be any downside to that?

Not really actually. Saying that we support gzip is fine IMO

@MorrisJobke
Copy link
Member Author

I wonder if this should be generally the default for our http client. Would there be any downside to that?

I would keep it like that for the backports and enable it for 20 in the default client?

@MorrisJobke
Copy link
Member Author

CI is fine -> merge

@MorrisJobke
Copy link
Member Author

I would keep it like that for the backports and enable it for 20 in the default client?

#21054

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants