Whplus Blog

Berikut ini domain .TLD life cycle sesuai informasi dari ICANN

( Some registrar activity post-expiration may not be reflected in the life cycle chart above )

 

Anyone who keeps up with us knows that we’ve moved all of our shared and reseller hosting servers over to Cloud Linux. Here I’m going to go over what exactly Cloud Linux is, what it brings to the table, and some of the more technical aspects of it.

So, what exactly is Cloud Linux?

In a typical server environment, there are no hard limits in place for each user. There are of course things you can limit (PHP memory use, cron job execution, disk space, bandwidth, etc), but those aren’t the things users do that will hit you where it hurts. The majority of resource problems stem from CPU use, or disk IO, bad MySQL queries, and other runaway scripts. Before Cloud Linux, it was always a game of cat and mouse. We had to have our sysadmins get notified of the issue, login to the machine, locate the user and suspend whatever activity they were doing which was causing the problems. Pretty lame, right? We thought so too. Cloud Linux changes the game, not only for the end user like yourself but for us. Read the rest of this entry »

Saya baru saja membaca prediksi dari IDC, sebuah lembaga riset yang fokus pada Teknologi Informasi dan Komunikasi (TIK). IDC menyatakan bahwa negara-negara di Asia akan menikmati pertumbuhan TIK yang luar biasa, yang dimotori oleh China, India, Indonesia, Vietnam, dan Filipina. Kesempatan kerja dan berkarir terbuka lebar bagi Anda semua. Bahkan perebutan dan saling bajak tenaga kerja dibidang TIK sangat terasa.

Tanpa terasa, saya sudah berkecimpung di dunia TIK selama lebih dari 25 tahun. Beberapa pelajaran telah saya petik dan ingin saya bagikan kepada Anda semua. Namun demikian, sebelumnya saya ingin menyampaikan beberapa hal di dunia TIK, dan tantangan saya bagi Anda. Read the rest of this entry »

This article addresses what metrics to look for when assessing the benefits of your query cache.

1. Current Size compared with maximum available size. To calculate the percentage used value for the query cache you can use the following formula:

((query_cache_size-Qcache_free_memory)/query_cache_size)*100

N.B. query_cache_size is a variable, which can be found from a show variables like ‘query_cache_size’; command. Qcache_free_memory is a status variable which can be retrieved from show status like ‘Qcache_free_memory’;

2. The Query Cache Hit Rate

The percentage hit rate on the cache can be calculated as follows:

((Qcache_hits/(Qcache_hits+Qcache_inserts+Qcache_not_cached))*100)

This percentage figure shows how much the query cache is used e.g. the figure in the screenshot of 33% says that of all select statements executed, 33% of them can be satisfied by the cache and hence do not have to be re-executed.

3. Hits to Insert Ratio and Insert to Prune Ratio

These two ratios are calculated by the following two formulae:

Qcache_hits/Qcache_inserts

Qcache_inserts/Qcache_prunes

A ratio of Hits to Inserts is displayed in order to show the Query Cache effectiveness. A high ratio of hits to inserts tells us that there are lots of identical SQL statements being run on the database and are therefore being serviced directly from cache. A low ratio shows that the cache is not much utilized.

The ratio of Inserts to Prunes represents how many times SQL queries are being inserted into the cache compared with how many times a query is being removed from the cache (pruned). This is also a good indicator of SQL reuse on the database and hence query cache effectiveness.

Berikut ini panduan untuk melakukan upgrade server CentOS ke kernel grsec-patched. Saat panduan ini ditulis menggunakan versi grsec-patched stabil terbaru yang tersedia.

Download source:

wget http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.15.tar.bz2
wget http://www.grsecurity.net/stable/grsecurity-2.1.14-2.6.32.15-201006191115.patch

Ekstrak:

tar xjf linux-2.6.32.15.tar.bz

Patch kernel:

patch -p0 < grsecurity-2.1.14-2.6.32.15-201006191115.patch
cd linux-2.6.24.5 && make clean && make mrproper

Copy konfigurasi kernel sebelumnya:

cp /boot/config-`uname -r` .config

Edit kernel:

make menuconfig

Pilih setting/konfigurasi sesuai keinginan anda. Jangan lupa untuk memilih konfigurasi “Grsecurity option” pada “Security Options”.

Compile dan install kernel:

make && make modules && make modules_install && make install

Pastikan seagalanya berjalan tanpa error:

depmod 2.6.24.5-grsec

Edit file /boot/grub/menu.lst:

nano -w /boot/grub/menu.lst

Terakhir reboot server:

shutdown -r now

Tunggu sampai server up lagi dan cek kernel yang terpasang. Selamat mencoba