Archive | tips RSS for this section

Tweaking Swappiness Setting in Linux

The default value setting for swappiness is 60. Meaning that the swap file will be used fairly often if the memory usage is around half of your RAM. Some suggested that reducing the default value of swappiness will probably improve overall performance for a typical Linux desktop installation. A value of swappiness=10 is recommended. The swap file will then only be used when my RAM usage is around 90 percent. Feel free to experiment.
To change the system swappiness value, open /etc/sysctl.conf as root. Then, change or add this line to the file:

vm.swappiness = 10

Reboot for the change to take effect.

Source:
How do I configure swappiness? | Ask Ubuntu
Why most people recommend to reduce swappiness to 10-20? | Ask Ubuntu
Why is swappiness set to 60 by default? | Unix & Linux Stack Exchange

Advertisements

Speeding Up Firefox by Disabling ‘Silent Request’

firefox-logo

To disable the ‘silent request‘, just set value of network.http.speculative-parallel-limit in about:config to 0
1. Type about:config into the address bar (and you’ll see a bunch of variables)
2. Copy and paste network.http.speculative-parallel-limit into the search bar at the top of that page and hit Enter.
3. You’ll now just have that one line on the page. Double-click it, a box pops up, you change the value to 0, and hit OK.

And that’s it.

Source:
How to Quash Firefox’s Silent Requests | Slashdot

Advices on Creating Web API

Publish the whole thing and make sure it is all well documented. Also, don’t hide functions through obscurity.

>> some types of customers don’t need to see all of the API in the library
Don’t try to go down that road. If you start hiding functions through obscurity, they will pop out anyway (through code samples, forums, reverse engineering, pentesting, etc.) and will only lead to bad things (developers pissed at you for “crappy, incomplete documentation,” customers laughing at you for “trying to hide the best stuff,” salespeople people yelling at you for not exposing something you’ve already written but they didn’t know they needed until they walked out of a customer meeting, top executives yelling at everyone when a security researcher finds a big flaw in a rarely used function call that everyone forgot about).

Signed,
Dude With 15 Years Experience With Web APIs
(Who Has Had Much Of This Happen To Him Or His Company)
xxxJonBoyxxx

Publish the whole thing and make sure it is all well documented.
When we evaluate products, one thing I always look for is a well documented API with full functionality.

Then endure your internal developers use it and eat their own dog food.
Anonymous Coward

Source:
Ask Slashdot: Best API Management System? | Slashdot

Turn on Tracking Protection in Firefox to Make Pages Load Faster

set privacy.trackingprotection.enabled to true

To turn on Tracking Protection in Firefox:

  • Type in about:config in the location bar and hit enter.
  • You’ll see a warning about possibly voiding your warranty. Hit “I’ll be careful, I promise!” to continue.
  • Search for privacy.trackingprotection.enabled.
  • Double-click that to toggle the value to true.

Former Mozilla software engineer Monica Chew and Computer Science researcher Georgios Kontaxis took a look at the top 200 news sites (according to Alexa) and found a median 44% reduction in page load time, as well as a 39% reduction in data usage when the optional Tracking Protection is turned on.

Tracking Protection actively blocks domains known to track users. You might not see huge performance benefits for all sites, depending on how much each site relies on third-party content and similar extras from tracking domains. Still, with a range of between 20% and 90% decreased page load times according to the study—and better privacy control—it’s worth a shot.

Source:
Turn on Tracking Protection in Firefox to Make Pages Load 44% Faster | Lifehacker

Common Tips to Read Programming Books

Some tips to keep in mind:
It’s not a sprint, it’s a marathon.
No need to rush all the way to the end of the book. Complete just one or two chapters per day. Never let your eagerness burn you out.

You MUST write all of the code yourself.
This is a good ol’ advice. Coding just won’t stick in your head without writing all of the code yourself. Resist the temptation to copy and paste.

Learning by doing is good.
Don’t worry if you don’t “get” what you’re doing right away. Just writing code will lead to plenty of “A-ha!” moments.

Taking a break is a legit solution.
If you get stuck, try taking a break.

Programming is not a memory game.
No need to remember every detail you learn. The main goal is to learn how to think about solving problems. From that point, Google becomes your greatest ally.

You need support.
Surround yourself with people who can support you in doing what you want to do.

It’s meant to be fun.

Codingcraft is hard, but it’s a lot harder when you lose sight of why you wanted to write code in the first place.

Reference:
meteortips.com

Tips on Building Homebrew NAS

Really helpful tips on building NAS system I’ve found on Slashdot.
Start quote.
Lessons learned from my dabbling with FreeNAS (and having hardware failure).
-Use generic HDD controllers that are supported in the box. (Using a 3rd party controller and driver, only to discover that when it reports an error, it becomes unavailable altogether, reboot to start again)
-Understand the features you are using. When I started, I configured a ZFS array with two hot spares, when a couple drives failed, the hot spares didn’t activate, and I was stuck…
-Practice a version migration early on.
-Use a motherboard with ECC Ram if you’re using ZFS, I can’t understate this enough. AMD CPU + ASUS Motherboard seems to be your best bet here for Unregistered ECC memory in terms of bang for the buck.
-Use as much memory as possible… if you can use 32GB of ram, do so.

In general, it was fun while it lasted, right now, I put 4x 4TB drives in my old Synology 409 box, and it’s running okay… I’m going to get one of the 12-drive synology boxes in a few months and test my old drives, putting them all in that moving forward. I really don’t have the time and patience for dealing with a homebrew NAS.

I don’t mean for this to discourage anyone, only pointing out that it’s sometimes far easier to buy an appliance that DIY.

End quote.
Source:
FreeNAS 9.3 Released | Slashdot