Hmm... as the zram device grows, less physical memory is available for actual application use. It seems I can get up to about 1.7-2.0 GB of swap utilization before we run out of physical memory and the system slows to a crawl.
(with the zram device using ~500-600 MB to store about 2 GB of swap data)
There's a positive feedback loop involved: as the zram grows, more data needs to be swapped into it, and the zram device grows further. This means it could take a while for everything to swap into it and to free up enough physical memory for normal operation.
But the fact that there's less free memory for application use does not help. A zram device taking up 1 GB of physical memory leaves 1 GB minus system-reserved memoey for active usage because apps can't run directly from the swap.
At least it does enable more apps to be kept in memory before swapping to disk becomes necessary.
So... going forward, it seems a sensible max size is something like 1.5 GB.
iostat indicates that some 28 GB of data got written to the zram device. That definitely points to some really bad thrashing.
Yes, zram does impact battery life due to increased CPU utilization, but the impact appears to be lower than using a power-hungry portable SSD as a swap device and performance is a bit better.
I am new to linux and AWS.
I ran sudo chmod 2770 / command on my ec2 instance and after that
I was getting Permission denied on everything I was doing(even using
ls or cd)
So I exited my connection(using cygwin) and tried to re-connect but now I get
Permission denied (publickey...
Docker doesn't expose any ports within containers by default, so the host machine isn't going to see port 80 as it appears to the code in each container.
It might not suffice, because company DNS might resolve "thing.test" to 192.168.1.x, which is reachable by the localhost but not by the docker container, as they reside in different networks.
well, I would need to point thing.test in the "php" container to be the same as apache (compose's internal domain name for webserver) ... if I got it correctly
I'm not too familiar with the topic but I do know that ports aren't going to be exposed to the host machine unless you tell Docker to specifically expose those ports from within the container.
@tereško So, broadly, there's two possible configs: docker can have its own network (so docker <=docker network=> host <=other network=> public internet etc) or they can share a network stack.
In the first config, as far as the container sees it, the host is a separate machine entirely. Localhost will never connect to it.
In the second config, localhost on the container means the host.
hmm .... there is a company-wide entry in the DNS for *.thing.test to point to 127.0.0.1, but the some.thing.test isn't actually defined anywhere - it's just a vhost on apache
Containers do not see the outside network unless you tell Docker otherwise. localhost inside the container is the container itself, not the host machine.
Now you need to either use the correct host IP (which may be accessible via a different domain name), or set up docker such that the container shares the entire network stack with the host.
though it looks like aliases can only be hostname, possibly
really, the better solution is to either use a proper public (or 'private', not loopback) IP address for your main domain definition
otherwise you end up with multiple DNS server shenanigans where which DNS server you connect to determines which IP you get back
there's many hacky ways you could get this to work
but if it's not a one-off, doing it properly is probably worth doing
(there's also questions like are you intending to distribute the docker containers/run them on other machines? that would limit how much you can hardcode)
An English teacher said "I'm really impressed by Rahul's command of the English language, and have very high expectations from him" and that's the nicest thing anyone has said to me in a loooong time and made me really happy
Eject the cd/dvd drive
Stress the CPU - listen for fan sound.
Download a large file, seeing which HDD light stays on.
If you have access to a switch - check the mac address table to see where it's plugged in
Power it off!
using dmidecode see which serial it is, check the serials on the physical ...
I am new to linux and AWS.
I ran sudo chmod 2770 / command on my ec2 instance and after that
I was getting Permission denied on everything I was doing(even using
ls or cd)
So I exited my connection(using cygwin) and tried to re-connect but now I get
Permission denied (publickey...
