Professional in Drupal web development, theme designing, consultation and training


Segalanya mengenai Drupal

Drupal: Duplicate content

26 Jun 2010 - 03:37 pm

When we talk about duplicate content, it is not talk about the content. From what I know and doing a lot of study, it also consist the whole page structure. From coding until content. One page considered similar to another when there is 75% is same.

Meaning that, I need to make one page to another page almost 75% unique compare to each other. It really hard to make a page that not really similar with others when you are using CMS or dynamic system management.

Why? Because mostly of this kind system either Drupal, Joomla, Wordpress or Php-Nuke will keep using and display the same thing and region. Such like menu, block or links. If you look at one page that generate by this system, it will keep display this area too all pages.

Common terms like "left sidebar", "right sidebar" contain same element in most of pages. When you right an article, the unique area is only content but the rest are same. So, how to solved this problem because you can not reach 75% unique page.

What you need to make it unique is put random or dynamic content in one page element. Suggested element:

  • You may like this
  • Related article/content
  • Random images/links
  • Other promotion

By adding this element, I can increase the number of unique coding and unique content in a page. And most of these element is generate based on main content. That mean, if i wrote an article about "Duplicate content", block that display "Related article" will try to find similar article regarding to the content.

But when user click or go to the related content, this block will generate another list that related to the content and not same with other page. Using this method, I have increase unique coding at Drupal Note from 25% to 77%.

Drupal Module: High Processing Related

15 Jun 2010 - 08:56 pm


Drupal 6.17

Here are list of Drupal's module that may lead to WSOD because of high processing during cron running or manually retrieving update status. All of these list comes from my experiencing using them. You can add more and I will update here.

  • Search Lucene -- cause server load to high when re-indexing data during cron run
  • Backup and Migrate -- used a lot of resources during backup and zipping files
  • SWF Tools -- this module gain resources during module enabling and status update

Drupal: Boost vs Authcache

14 Jun 2010 - 09:24 am

In my previous entry, I have talk about Boost module installed in my blog. And such it was really such a great module. After KS have been attacked by various IP through DDoS method, then I make that site also being boosted by this module. Server processing reduce follow by request and server load also perfectly low.

But currently Boost module still have bugs when Drupal is integrating with other CMS system, which in my case it have been connected with phpBB. This is because, everytime user need to login, they need to surf 1 or 2 pages first before cookies will be synchronized between two system. So the problem when every time users closed their browser and re-open, login form showed logout. 

This is because boost page cache the dynamic page into static HTML which already set the cookies as "anonymous user".Although there still a valid cookies set, .htaccess will determine as non-cookies have been set before. So, although I boost the performance but there's a lot of complaint about that. Actually, Boost module was design to be used in site that serve static page for anonymous user like blog type.

As the solution, I have try Authcache (Authenticated User Cache) module that serve function just like Boost module but in different method. This module speed up Drupal bootstrap through caching a normal processing and hits through database in one table. While a light bootstrap processing was hit just to decide either it need to hit database or take result from cache table. So, it can be used for anonymous and authenticated user.

After installed, then I run performance testing for anonymous user to compare between Boost and Authcache. And the result just like below:

Boost module much speed up in sending bytes compared to Authcache because it send static HTML while Authcache still sending dynamic content to user. Both module provide caching method at same par since pages start to render at the same time. Because Authcache provide much big file to be downloaded, so I need to force page being render main content first. So that excluded other region like left and right regions from render at the same time.

To make it, I installed assist module called Ajaxify Regions which it make all region except "content region" to load after the whole document complete download. That tell the different size between "Document complete" and "Fully loaded" stats. The different in size is about 40kb.

With Authcache module, problem about synchronization of cookies have been solved. What can I say is:

  • Boost module is perfectly for site that serve mainly for anonymous users
  • Authcache module is perfectly for site that have many registered users

Drupal: Boost, Really Boost My Blog

04 Jun 2010 - 10:28 pm

In my previously entry, I have talk about my blog performance with all details about time spending on downloading and load the whole blog. And also about the time start to rendering. My blog performance have been tested at New Zealand server which is quite far from the origin server. Before doing the testing, some tweaking have been done. Such as php flushing, reducing number of modules installed and highly caching of Javascript and CSS files.

Drupal basically have built-in the caching system in the core which will cache and aggregate multiple JS and CSS into one files. This will reduce the number of HTTP request and minimize the size for fast downloading. By set mode of cache into "normal" or "aggresive", my blog rendering increase in 30% more faster. With activated of GZip mode, I have save my bandwidth for about 30% more.

Although Drupal have ability to cache all page generated but it only effects the anonymous users. Site with a lot of registered members would back to normal performance once they log in. A blog site usually doesn't really need any guest to registered either to leave a comment or to read any entry, this ability really give benifits to my blog.

Although I have done a lot of tweaking, but it can not challenge HTML files because it is the fasters format to be load. Although PHP server will convert everthing it process into HTML format, it still taking some time. Any request from user will go through .htaccess file, then passes to Drupal PHP files, retrieved information from database, process it again and pass to webserver to provide HTML files to user. This journey taking about 1 to 1.5 second.

With Boost modules installed in my Drupal, at the end of process it will store the HTML files into cache folder. When the same request (meaning the same file) is send, this module will directly take HTML files in cache and send it to user. This process only consume about 0.5 sec. Believe it or not, the different is about 1 to 1.5 second. I suggested any blog out there that using Drupal as your main system of blogging, used this module. It's really easy to setup.