I will most likely not be able to take part in our meeting tonight, at the very least I will be late. Here is a brief summary from me: I don't think I have really worked on much openSUSE related in February - only minor maintenance stuff and some tickets. * I tried getting the indexing to work on mailman3, Lars allocated some more memory which meant the process ran a lot longer - until it ran out of disk space. When someone has a moment, /dev/vdb on mailman3 could probably do with twice as much space. progress.o.o #88903 * there is a recent ticket from the KDE admin about failing DKIM checks for reports from bugzilla.suse.com - as well as new one about 'suse.com' users being unsubscribed from factory which could be due to DKIM validations failing. I have not yet looked at it in any detail. progress.o.o #89332, #89227 * to amuse myself, I have added some caching (Expires: header) on forum.o.o, to see if caching the most requested static objects would reduce the traffic. Sofar not much effect, not sure why. -- Per Jessen, Zürich (12.4°C) Member, openSUSE Heroes
Hi Per, @ll
I'm sorry, but some private stuff is blocking me attending the meeting.
I've anyway not much to say: just working on tickets and the usual
maintenance stuff during the last days.
Am Tue, 02 Mar 2021 14:37:38 +0100
schrieb Per Jessen
* I tried getting the indexing to work on mailman3, Lars allocated some more memory which meant the process ran a lot longer - until it ran out of disk space. When someone has a moment, /dev/vdb on mailman3 could probably do with twice as much space. progress.o.o #88903
Space problem should be solved meanwhile.
* to amuse myself, I have added some caching (Expires: header) on forum.o.o, to see if caching the most requested static objects would reduce the traffic. Sofar not much effect, not sure why.
Did you add it on the server itself or also on the haproxy side? I'm not 100% sure, but IMHO haproxy is configured to remove/re-add some headers... Regards, Lars
On 02/03/2021 19.51, Lars Vogdt wrote:
* to amuse myself, I have added some caching (Expires: header) on forum.o.o, to see if caching the most requested static objects would reduce the traffic. Sofar not much effect, not sure why. Did you add it on the server itself or also on the haproxy side? I'm not 100% sure, but IMHO haproxy is configured to remove/re-add some headers...
Header is there: curl -I https://forums.opensuse.org/images/misc/arrow.png HTTP/1.1 200 OK Date: Wed, 03 Mar 2021 06:29:21 GMT Server: Apache/2.4.43 (Linux/SUSE) Strict-Transport-Security: max-age=31536000 X-Frame-Options: SAMEORIGIN X-XSS-Protection: 1;mode=block X-Content-Type-Options: nosniff Last-Modified: Mon, 10 Nov 2014 15:14:41 GMT ETag: "74-507829f299a40" Accept-Ranges: bytes Content-Length: 116 Cache-Control: max-age=604800 Expires: Wed, 10 Mar 2021 06:29:21 GMT Vary: User-Agent Content-Type: image/png X-Forwarded-For: (null) IIRC in absense of such headers, browsers had a caching heuristic using the ratio between Last-Modified and when they last checked, so you do not get any improvement. Also a week is not that long - there might be users checking forums less often. And there seem to be a lot of different small images used. e.g. 29 on https://forums.opensuse.org/forumdisplay.php/668-Install-Boot-Login Maybe some pre-loading could improve user-experience there.
Bernhard M. Wiedemann wrote:
Header is there:
curl -I https://forums.opensuse.org/images/misc/arrow.png HTTP/1.1 200 OK Date: Wed, 03 Mar 2021 06:29:21 GMT Server: Apache/2.4.43 (Linux/SUSE) Strict-Transport-Security: max-age=31536000 X-Frame-Options: SAMEORIGIN X-XSS-Protection: 1;mode=block X-Content-Type-Options: nosniff Last-Modified: Mon, 10 Nov 2014 15:14:41 GMT ETag: "74-507829f299a40" Accept-Ranges: bytes Content-Length: 116 Cache-Control: max-age=604800 Expires: Wed, 10 Mar 2021 06:29:21 GMT Vary: User-Agent Content-Type: image/png X-Forwarded-For: (null)
IIRC in absense of such headers, browsers had a caching heuristic using the ratio between Last-Modified and when they last checked, so you do not get any improvement.
That I was not aware of, but it matches what I am seeing :-)
Also a week is not that long - there might be users checking forums less often. And there seem to be a lot of different small images used.
That's true - I'll try it with a month instead. -- Per Jessen, Zürich (4.9°C) Member, openSUSE Heroes
Citeren "Bernhard M. Wiedemann"
curl -I https://forums.opensuse.org/images/misc/arrow.png HTTP/1.1 200 OK ^^^^^^^^
If improving user experience is what you're after, in my experience enabling HTTP/2 is very helpful. You'll already reap a lot of benefit by just enabling the module in Apache (without any further setup).
Per Jessen wrote:
Bernhard M. Wiedemann wrote:
Header is there:
curl -I https://forums.opensuse.org/images/misc/arrow.png HTTP/1.1 200 OK Date: Wed, 03 Mar 2021 06:29:21 GMT Server: Apache/2.4.43 (Linux/SUSE) Strict-Transport-Security: max-age=31536000 X-Frame-Options: SAMEORIGIN X-XSS-Protection: 1;mode=block X-Content-Type-Options: nosniff Last-Modified: Mon, 10 Nov 2014 15:14:41 GMT ETag: "74-507829f299a40" Accept-Ranges: bytes Content-Length: 116 Cache-Control: max-age=604800 Expires: Wed, 10 Mar 2021 06:29:21 GMT Vary: User-Agent Content-Type: image/png X-Forwarded-For: (null)
IIRC in absense of such headers, browsers had a caching heuristic using the ratio between Last-Modified and when they last checked, so you do not get any improvement.
That I was not aware of, but it matches what I am seeing :-)
I looked it up, it seems that most browsers, in the absense of any caching instructions, default to "10% of today-lastmod", but maximum 1 week. That certainly explains why I have not seen any major improvement sofar. -- Per Jessen, Zürich (6.8°C) Member, openSUSE Heroes
On 3/3/21 10:48 AM, Per Jessen wrote:
Per Jessen wrote:
Bernhard M. Wiedemann wrote:
Header is there:
curl -I https://forums.opensuse.org/images/misc/arrow.png HTTP/1.1 200 OK Date: Wed, 03 Mar 2021 06:29:21 GMT Server: Apache/2.4.43 (Linux/SUSE) Strict-Transport-Security: max-age=31536000 X-Frame-Options: SAMEORIGIN X-XSS-Protection: 1;mode=block X-Content-Type-Options: nosniff Last-Modified: Mon, 10 Nov 2014 15:14:41 GMT ETag: "74-507829f299a40" Accept-Ranges: bytes Content-Length: 116 Cache-Control: max-age=604800 Expires: Wed, 10 Mar 2021 06:29:21 GMT Vary: User-Agent Content-Type: image/png X-Forwarded-For: (null)
IIRC in absense of such headers, browsers had a caching heuristic using the ratio between Last-Modified and when they last checked, so you do not get any improvement.
That I was not aware of, but it matches what I am seeing :-)
I looked it up, it seems that most browsers, in the absense of any caching instructions, default to "10% of today-lastmod", but maximum 1 week. That certainly explains why I have not seen any major improvement sofar.
Bear in mind that a browser cache does not have infinite size or sometimes gets just cleared. So even choosing a longer cache TTL at the server side does not necessarily result in a higher cache rate. Also long caching TTLs can be pretty annoying for end users after upgrading the server software. Ciao, Michael.
participants (5)
-
Arjen de Korte -
Bernhard M. Wiedemann -
Lars Vogdt -
Michael Ströder -
Per Jessen