Drupal database loading slow

Question

I'm making a website (don't open in IE) where I use Ajax to load a view. I now want to use BOOST to cache the view as HTML.

These pages should be "BOOSTED":

http://www.spanjevakantiewinkel.nl/regio/ajax/8 http://www.spanjevakantiewinkel.nl/regio/ajax/9 ...

Should I use JSON instead of my way to load the view? Any idea how?

The ID (8,9,...) is given by hovering a small image beneath the large header image. Then the view will be loaded, but always within the database, I want HTML pages made with BOOST.

function dynamic_regio_menu() {
  $items = array();

  $items['regio/ajax'] = array(
    'title' => 'Dynamic Regio',
    'page callback' => 'dynamic_regio_get_by_category_id',
    'access arguments' => array('access content'),
    'type' => MENU_CALLBACK
  );    
  return $items;
}

function dynamic_regio_get_by_category_id($cat_id){
    $viewName = 'regio_submenu'; // The name of the view we are going to load

    $args = array($cat_id);  // Array of arguments we set for the view.
    $displayId = 'block'; // The display id of for the view. 

    // Call the views_embed_view function to returned themed view output
    $html = views_embed_view($viewName, $displayId, $args);
    echo $html;
}

xhr = $.ajax({
  type: 'POST',
  url: '/regio/ajax/' + this.parentNode.getAttribute('tid'),
  success: updateData, dataType: 'html',
});

Answer 1

I think the problem is how your views are cached - if you say it is sometimes slow, it is most probably because those times the cache is beeing saved. If the content doesnt change often, you might just prolongue the interval. Another option is to use Views content cache. But basically if you have enough visitors (and enough people hovering the images :), they will only wait from time to time ...

Answer 2

The Query time is simply the time it took for the DB to send the result of the query to be returned. The page execution takes into account all of the processing of those results.

This is why it's so important to have Caching enabled.

This may explain more of Views caching: Are views cached through the core caching mechanisms or should I be setting the caching directly in each view?

Answer 3

I am not sure if it can help or not but when I try to make ajax I have to call drupal_exit() I don't want drupal to get all page element just this string

function dynamic_regio_get_by_category_id($cat_id){
    $viewName = 'regio_submenu'; // The name of the view we are going to load

    $args = array($cat_id);  // Array of arguments we set for the view.
    $displayId = 'block'; // The display id of for the view. 

    // Call the views_embed_view function to returned themed view output
    $html = views_embed_view($viewName, $displayId, $args);
    echo $html;
    drupal_exit();
}

Answer 4

I would definitely advise to check if you have removed modules that are still enabled. This is a real performance killer because Drupal is searching for the module files.

The behavior that you describe looks like this issue.

Answer 5

OK, I know this is an old thread, however, I just went through quite a bit of trouble with this and thought I should post here so others will know what my problem was.

first and foremost, verify that your view is not trying to render every single node and comment in the content type if there is a lot of content! It will dismally slow the site doen even if you are using caching, etc. The problem only manifested itself after migrating 56000 or so comments onto 30000 nodes.

The pager count evidently counts nodes and comments and my view had a contextual filter for the logged in user that was not working as it should. Once I got it working, the views are fast and everything is good so I hope this helps someone down the road.