@dreamcatch22 with AWS, I have usually found that it's either

a) the cpu credits are kicking in. are you aware of https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-credits-baseline-concepts.html ? AFAIK, even lightsail has the same limitation (but not 100% sure).

b) some machine have a lot of memory but perform very poorly . For example, see the notes in EC2 R5 xlarge (which has 32GB RAM!) but works very poorly with docker - https://forum.cloudron.io/post/17488

Not sure, if either of those apply to you. What instance are you using ?

@lonk said in Apache, OLS and Nginx-Custom Benchmarks:

redis is already apart of Cloudron

Yes & no,
Yes is part of the cloudron addon, but it can be integrated in different way.

You can use it for dynamic cache (as cloudron use in there apps), behind the php, db lvl.

You can use it as a Full Page Cache (similar to what Cache Enebler do but in RAM and not in local disc). php lvl

You can use it for partial page caching, in this case is at webserver/proxy lvl.

Redis is just a "database" in RAM, you can use it to store what you want, Redis is not a cache, but you can use it as it was one.

Faster networking with TCP BBR.
https://omgfoss.com/enable-tcp-bbr-ubuntu-speedup-network/

Append to bottom of /etc/sysctl.conf

# BBR Faster Networking net.core.default_qdisc=fq net.ipv4.tcp_congestion_control=bbr

@fbartels said in MySQL tuning with my.cnf settings optimisation:

@lonk said in MySQL tuning with my.cnf settings optimisation:

when do we run / apply it?

Mysql tuning is best applied after a few days of database usage. Applications usually have different load patterns.

Gotcha, thanks for the tip! ☺️

The CPU share setting is a percentage relative to each app. So, you should make tinytinyrss slider to be 20%. That way, it will take less CPU compared to other apps (which are set to default to 80%).

There's a more detailed explanation here - https://www.batey.info/cgroup-cpu-shares-for-docker.html . When 50%, we set the CPU shares value to be 50% of 1024, when 20%, we set the CPU shares to 20% of 1024 and so on.