Wednesday, September 10, 2008

Make AdSense For Revenue

AdSense Tip #1: Find your keywords

Make a research the best keywords.

AdSense Tip #2: Improve your keywords

Make sure your keyword density between 3% to 10 %.

AdSense Tip #3: Keep your website focused on a theme

Do not mix you content.Focus on your main theme and content.

AdSense Tip #4: Write a new page every day

Always update your site or blog. If you can,updated daily.

AdSense Tip #5: Choose the right AdSense formatÂ

Choose the best ads format for your site.Top ads format that suggest by google is:

  1. 336×280 large rectangle
  2. 300×250 medium rectangle
  3. 160×600 wide skyscraper

AdSense Tip #6: Color tips

AdSense Tip #7: Position tips

AdSense Tip #8: Increase the number of ads

Maximized the usage of your ads.

AdSense Tip #9: Use images

Use images to combine with your ads.

AdSense Tip #10: Blend

Trace - Debug ( Profiling ) PHP script by xdebug & kcachegrind

Step 1 : Install XDebug

xdebug is an open source debugger available for PHP. xdebug can be used to display more information in error traces. It can also be used to collect detailed code coverage & profiling information.


You need to install following packages to prepare environment for installation of pecl module xdebug.

sudo apt-get -y install php-pear php5-dev build-essential

Now we install xdebug using pecl.

sudo pecl install xdebug

Above command will download, compile & install xdebug on your system.


Open usr/local/lib/php.ini and append following line.


Be careful about that number part in the path as it could be different for you. Now restart apache by issuing following command.

sudo apache2ctl restart

Now try to view the output of your phpinfo() function. If you find xdebug word in that then it means you have successfully installed xdebug.


xdebug.collect_params accepts values from 1 to 4. Where 1 refers to less verbosity & 4 refers to maximum verbosity while displaying stack traces. The easiest way of setting this option is using function ini_set in PHP.

ini_set("xdebug.collect_params", )

Get to know more stack trace options of xdebug.


Once after installing xdebug when ever you call var_dump you are actually calling xdebug version of var_dump instead of built in one. By default xdebug version of var_dump gives you friendly info on the variables you are trying to inspect.

See more options on controlling display of var_dump information.


xdebug uses DBGp protocol to communicate with external debuggers. Vim already has a plugin to do that. So you can debug php scripts from within vim.

Download php debugger plugin for vim.

Step 2: Enable Profiling

You need to add following line to /usr/local/lib/php.ini to enable profiling of php scripts.

Now restart the apache server by issuing following command.
sudo apache2ctl restart

When ever you access a php page through apache, xdebug will create a file something like cachegrind.out.15093. xdebug by default uses /tmp directory to dump files which contain profiling information. You can change this target directory by using xdebug option xdebug.profiler_output_dir and you can change result file name by using the option xdebug.profiler_output_name.

See more xdebug profiling options.

Some times you don't want to profile all requests. xdebug provides a selective mechanism to trigger profiling of specific requests. In order to enable this option you have to add following configuration option to php.ini.

Now you can trigger profiling of specific requests by adding XDEBUG_PROFILE to the query part of the GET request.

Analyzing Profiling results

We need to use kcachegrind to analyse profile file results. We can install kcachegrind by issuing following command.

sudo apt-get -y install kcachegrind

Now open your profle result file in kcachegrind and you can visuall inspect which part of your script is eating cpu resources. Callmap & Callgrap provide easy to understand visualizations to find bottlenecks in your script.