ptprog

When using a rule of type "Reaction is given", what is the meaning of the milestone? For example, if we set it to "It is their 10th reaction", will the rule be applied: When a specific post receives the 10th reaction? When a user receives the 10th reaction considering all posts? When a user gives the 10th reaction considering all posts? Other? In other words, is the milestone for the user giving the reaction, or for the receiving user? And do we count the reactions on a specific post, or for all posts? (I actually think all the variants should be supported, but for now I'm wondering which one is currently implemented.)

Ok, so you certainly have spare memory available on you server 😄 You should try Redis. If you have some analytics solution, you should be able to monitor the evolution of the performance on your site.

I haven't looked in detail about how IPS uses cache (e.g. how expensive to compute are the values cached), but with the reduced number of options we have now, and assuming you have spare memory available, I expect Redis to be a safe bet. IPS can achieve very high cache hit ratios. So, my expectation is that using cache will improve performance. Since now using cache requires using Redis for data storage, I would be surprised if any other data storage option was better. Again, I'm assuming you have spare memory in your server. Also, as @Thomas P mentioned above, using Elasticsearch for search may be a better change to start with. Out of curiosity, what is the current size of you DB?

From what I can see, in recent versions you either use Redis for "Data Storage Method", or you won't be able to select any "Caching Method" (i.e. to use Redis as "Caching Method", you also need to use Redis as "Data Storage Method"). So, I guess Redis is the way to go.

I usually put a lot of effort on website optimization, and I certainly would like to see IPS paying more attention to performance. But looking at results from other popular websites such as Youtube, Facebook or Amazon, the values are not that different. I checked a few other landing pages from Google, with mostly static content, and the results were even worse. So, I guess IPS is not that bad.

If you are familiar with cache headers, you can just use Chrome developer tools (in the Network tab, you can see the headers of each, and check the expiration time, e.g. "expires: Sun, 07 Feb 2021 08:27:40 GMT" shows the cache expires in 1 month). You can also use Google Pagespeed (Serve static assets with an efficient cache policy) or www.webpagetest.org, for exemple, which provides higher-level details (as @Mopar1973Man also suggested). BTW, I'm wondering if some of those cache "issues" may be caused by Cloudflare, since the cache expiration sometimes of some images varies depending on the tool you use to test. If this is the case, maybe it's due to some online optimization made by Cloudflare, and you may not be able to fix it. I would still make sure that when you hit your server directly (bypassing Cloudflare), the resources have cache.

Any plans for adding solved content to leaderboards?

Not sure if you already solved your issues, but it seems the initial server response time is huge (2 to 3s, whereas this value should be below 1s). Another issue you have is the cache expiration of static resources. It seems the fontawesome-webfont.woff2 has no cache expiration set at all. And the JS, CSS and images files have a cache expiration of 30 days. Since these resources use cache busters, you should be fine setting a much longer cache time (6 months, or even 1 year).

Do we really need to do anything about that? It would be like forbidding users to mention the other user name, which does not make sense to me. I'm not a lawyer, but I have serious doubts the GDPR gives users this right.

@Adlago if you replace the line you show with <link rel="manifest" href="{url='app=core&module=system&controller=metatags&do=manifest' seoTemplate='manifest'}" crossorigin="use-credentials"> the new connection issue is solved. (I tested this, and it solved the issue in my case.) BTW, after start using SSL and HTTP/2, my tests (using RUM) showed that the use of cookie-free domains was only slightly beneficial when I was using a CDN. Otherwise it was degrading performance, despite most of the synthetic tests (like YSlow and Webpagetest) giving better results. This was before TLS 1.3 was available. It is possible that with TLS 1.3 the results change.

Not sure what IP addresses you are referring to, but this is likely intended behavior. Not all IP addresses are removed, which makes sense as some IP addresses (such as the ones associated with newsletter opt-in, or privacy policy acceptance) can be seen as part of the proof of consent. However, there are several other IP address that are not deleted, and for which we don't have good reasons to keep. (To solve this issue, I checked the IPs that were not being removed, and I have a SQL script to periodically remove the ones I don't need to keep.)

Regarding performance, my experiments show a small degradation of performance (15% ~ 20%, measured with a RUM script) during the period I used the preload setting.

Has anybody tried to use '<link rel="preload" ...>' to load fonts? Any idea if this improves performance?

That option is enabled. The problem is the primary group 🙂 Thanks!