Home » Archive

Articles in the Tuning Category

Apache, Bugs, Debian, Featured, Glassfish, Headline, How-to, Java, Linux, Shell, Tuning »

[28 Sep 2009 | One Comment | ]

A lot of people are not satisfied by the default Java Logging (JUL) in Glassfish. Also, myself I encountered some problems on clustered environments where we should have one single log and not one log for each instance. Trying to change the logging system in Glassfish it looks to be almost impossible , but I found a very interesting project java.util.logging to log4j Bridge and the sky become more clear for Glassfish logging. Jul to Log4J Bridge are part of log4J project and is very useful when you …

Databases, Featured, Headline, How-to, Linux, Shell, Tuning »

[16 Jul 2009 | 4 Comments | ]

In my experiments with databases I was constrained to tune the system together with the databases. A system what will run a database is quite different from any other server system, because databases put a lot of stress on the IO and especially on the disks (probably the file servers too). Hardware is not all you should tune your system as much as possible. In this post I will talk about Linux with Ext3 (is what I have right now), but on future I will test OpenSolaris with ZFS.

(adsbygoogle …

Apache, Debian, Featured, How-to, Newbie, Tuning »

[22 Jun 2009 | 3 Comments | ]

Limiting abusers from running 20 download threads from the same Apache server is easy now with mod_limitipconn. But the apache 2 module, mod_limitipconn, is not available under the latest Debian distribution, Lenny. In this mini how-to I will show you how-to manage this module to work for Debian Lenny users. The compile process of mod_limitipconn is a little bit more than “make install”.
First install apache prefork development utilities (we need apxs2 to compile our module)

(adsbygoogle = window.adsbygoogle || []).push({});

Share this post

Databases, Debian, Headline, Linux, Mysql, Oracle, Postgresql, Shell, Tuning »

[18 Jun 2009 | 65 Comments | ]

We are living interesting times … MySQL was first purchased by SUN and now SUN was purchased by ORACLE. I don’t know what future will reserve for MySQL, but in this moment it seems MySQL is coming very very close to PostgreSQL. We are NOT talking about MySQL with MyISAM, we are talking about MySQL with InnoDB, because I’m directly interested in a set of properties what PostgreSQL already have them built-in and MySQL achieve them through InnoDB (and the new Maria Data plugin). This properties are Atomicity, Consistency, Isolation, Durability = ACID, in other words, very stable, good integrity and crash proof database. Why an ACID database? Sometimes we are more interested in ACID for our data than raw speed. For example do you keep your savings to a bank who is running a NON ACID database? I think you understand my concern.

Cryptography, Debian, Featured, Headline, How-to, Linux, Newbie, Recovery, Security, Shell, Tuning, Ubuntu »

[13 May 2009 | 3 Comments | ]

Gpg is stands for Gnu Privacy Guard and is a free alternative to the PGP cryptographic software. GnuPG (or GPG) follows the RFC 4880 which is the standard specification of OpenPGP. The most important thing GPG is interoperable with PGP. GPG is build as a command line utility but also have several front-ends for KDE, Gnome and other Linux desktops, but also is directly integrated in other software like: Email Clients as Mozilla Thunderbird, Evolution, Kmail, Instant Messaging as PSI, Fire, Browsers as Mozilla Firefox etc.

(adsbygoogle = window.adsbygoogle || …