Guess I'll use JPEG compression 8 or 9 by default on fast connections unless an application is genuinely color-critical (and yes, this can be changed without closing the connection). On my DSL at home, I'll use JPEG compression 6 and increase it only when needed for critical graphics.
5 and lower result in a significant degradation of graphical quality with little advantage.
JPEG compression 8 results in a slight loss of quality in high-contrast areas but maintains graphical fidelity for the most part. Lower compression settings result in progressively worse quality, although quality is acceptable for anything not pixel-critical down to around 5 or 6.
JPEG compression 9 is perceptually lossless. There's just no difference compared to disabling JPEG compression altogether except under critical analysis of the graphical data under the GIMP or other advanced image editor.
Compression artifacts start to become intrusive at 4 and below; hence, settings this low are not recommended unless the connection has exceedingly low bandwidth.
I ran a load test on the production server since I scaled it down. It's only getting 22 requests per second.
Not really an issue as the blog only gets a few hundred impressions a day, but this isn't ideal.
Most of the CPU load comes from PHP, as before, but because there is only one CPU core available, the amount of throughput available is reduced by more than half due to the added context-switch overhead (Fail2ban must analyze the logs in near-real-time while PHP generates the pages).
Well, 4 TB of transit a month doesn't allow a particularly large amount of sustained traffic.
An alternative is to turn UAC off completely and always run all programs as administrator. It's maybe not recommended but believe me, it's a relief.
In Vista you could turn it off in the control panel, in Windows 7 you must modify the registry (Note: This is NOT the same as the no nags setting w...
"Today we are going to share a simple installer which installs the required system files in Windows so that you can enjoy Group Policy Editor in all Windows 7 editions."
"According to some readers, this tool also works fine in Windows 8 and Windows 8.1."
$_ At shell startup, set to the absolute filename of the shell or shell script being executed as passed in the argument list. Subsequently, expands to the last argument to the previous command, after expansion.
In practice I find it easier to install Bash in Windows and just use it. For example, Git has a decent Bash environment that is easily installable in Windows. Even if you don't use Git.
@underscore: general piece of advice. Having kali installed does nothing. You really need to work on fundamentals and understanding why and how to do things.
Typically folk use the wifi card in kali for wifi cracking and stuff
If you just want to get online its a different thing.
heh. I just hit 110 accrued reputation on hardware recs.
@DragonLord ever since fedora moved from iptables to firewalld, my fail2ban doesn't work anymore (and I can't be arsed to fix it, since I use PK authentication)
openSUSE has its own firewall system (SuSEfirewall2) which relies on iptables as its backend. This isn't changing, it's core to the SUSE platform.
Fail2Ban should never break completely on openSUSE.
Firewalld is Red Hat's own solution. It's available for openSUSE, but I doubt it'll replace SuSEfirewall2.
Anonymous
@DragonLord all these changes: migrating to systemd was good and easy IMO but I don't fully master the-now-deprecated iptables and now I'm expected to know nftables and firewalld
Is there an alternative to gpedit.msc for "Home" versions of Windows (ie: Vista Home Premium)?
