UNIX for Dummies Questions & Answers

There was already a hint in the file:

See the man pages for "sysctl.conf" (chapter 5) and for sysctl (chapter 8), like this:

Code:

man 8 sysctl
man 5 sysctl.conf

No. Kernel parameters control all sorts of things, including what you believe to be their purpose. For instance:

Code:

# Controls IP packet forwarding
net.ipv4.ip_forward = 0

controls if IP packets arriving on one interface should be sent using another interface if they are not addressed to the host. If switched on this system would start to act as a router and you could put further software shaping/limiting/restricting this forwarding process ont it - firewalls and gateways are built this way, usually.

It is a sound decision to switch this off, because - as a design principle - every system should either act as a server or a router, but not both. As you want to build a RDBMS-system routing functionality should be out of the question.

The kernel parameters are organized in a "tree" structure: for instance, there is "net.*", controlling all sorts of network parameters, with the subtrees "net.ipv4.*", related to IPv4-parameters and "net.ipv6.*", related to IPng-parameters, etc.. Most of these values have defaults and usually only the values differing from the default are mentioned. As a rule of thumb you don't change any of these parameters if there is no necessity.

I suggest yo install Oracle, load the database, let the customers test and only then, when they complain about bad performance, you start to seek ways to meet their demands. The magic word here is:

Service Level Agreement

It is like a contract, where the customer defines exactly what he wants to have in some terms that are measurable (seconds, transactions, kilobytes, whatever - but it must be a COUNTABLE quality, not just gut feeling and "can you please adjust some wee bit, you know, make it faster overall".

In turn you guarantee to meet these demands and the customer agrees not to pester you any more as soon as this goal is reached.

Once there is such an SLA and the system is indeed not meeting it you can start researching ways to make the system meet these demands, but not before!

One reason for this is that there is a huge difference between performance and being fast. "Performance" means being fast for a specified purpose under specified circumstances. Here is an example for what this means: suppose a 40t-lorry, a 500hp-Ferrari and a Land Rover. Which one is the fastest (most performant) car? The answer to this is: that depends. It depends on which roads you want to travel (try going a hollowway in a dense forest with the Ferrari), how much goods you want to transport (the Ferrari will only have room for a credit card while the lorries cargo bay is considerably bigger, etc.. What you are trying to do is to tune the Ferraris compression ratio to make it 10hp more powerful before you even know if you need a Land Rover, a lorry or this racing car. This is simply wasting time.

I hope this helps.

bakunin