To enable more Devel module settings, including performance options, go to Site configuration | Devel settings or to here: http://variantcube.com/fire/admin/ settings/devel
This is where you can configure Devel to collect database query information and display query logs. Follow these steps to configure performance logging:
1. Check the box next to Collect query info if you want Devel to collect database query info.
2. Check the Display query log box if you want Devel to display a log of these database queries. The log will also display the execution time for each query. It will also keep tabs on repeated queries and note these in the logs in a separate # column. These queries will be highlighted in red to draw your attention to them and then you can decide whether you need to focus caching mechanisms on these specific queries to improve performance.
3. Tell Devel how you want to sort the query log—by source or by duration. We will leave sorting by source so that it displays them in the order of execution.
4. In the Slow query highlighting section, you can enter a baseline millisecond integer that the Devel module will use as its benchmark. Devel will highlight any query that takes longer than your sourced and benchmarked millisecond specification. This can also help you decide what needs caching on the site. Right now, we'll leave this set to the default of 5 millisecond.
5. You can also choose to store statistics about queries in your Devel database. We'll enable this and store every page view to start, as we're working on a development site. On a production site, you may not want to capture every page view, for example, raising this to capture every twentieth page view. This will help to stop our database table from overloading with statistics, but still allow us to capture some.
Collect query info
Collect query info. If disabled, no query log functionality will work. Display query log
□ ¡splay a lag of the database queries needed ta generate the current page, and the execution time for each. AIsq view are summed in the # column, and printed in red since they are candidates for caching.
Sort query log:
f* by source O by duration
The query table can be sorted In the order that the queries were executed or by descending duration.
Slaw query highlighting: É-
Enter an integer in milliseconds. Any query which takes longer than this many milliseconds will be highlighted in th query, or a candidate for caching,
E Store executed queries
Store statistics about executed queries. See the devel_x tables.
If storing query statlstlcsr only store every nth page view, i means every page viewr 2 every second, and so on.
6. The next setting is the URL for your API documentation. We'll just leave this set to the default Drupal API URL, which is api.drupal.org. Some developers store all of their API documentation locally, so if you do this you would want to enter your local URL/path here.
7. By checking the Display page timer box we can see page execution times in our query logs.
8. Check the box next to Display memory usage. We'll want to see how much memory we're using to generate pages.
9. Check the Display redirection page. This will prevent any query logs from being lost if a drupal_goto() function is run. We'll be presented with a redirect hyperlink path to the page that Drupal wants to direct us to after it shows us the query information.
10. Check the Display form element keys and weights box.
11. Another nice option here is the ability to skin your debug information. The Krumo display radio buttons allow you to pick a skin for your interface. Go ahead and choose one. I'll go with orange.
12. Because we're in the course of developing this site, let's check the box Rebuild the theme registry on every page load. We would not want to do this on a production site, as it could cause significant sluggishness, but while we're in development it's okay.
The base URL for your developer documentation links. You might change this if you run api,module locally.
w Display page timer
Display page execution time in the query log box.
Display how much memory is used to generate the current page. This will show memory usage when deveHnitQ is c been compiled with the --enabie-memory-limit configuration option for this feature to work.
When a module executes drupal_gotoQ, the query log and other developer information is lost. Enabling this setting the log can be examined before continuing to the destination page.
Display form element keys and weights
Form element names are needed for performing themeing or altering a form. Their weights determine the position keys and weights beside each form item.
C default G blue C green f* orange C schablon.com C disabled
Select a skin for your debug messages or select disabled to display object and array output in standard PHP format,
Rebuild the theme registry on every page load
While creating new templates and theme_ overrides the theme registry needs to be rebuilt.
13. Expand the Administration menu settings. This allows you to tell the Devel module to display additional information next to each menu item on your site. For now let's leave this unchecked.
14. Devel node access debug mode allows you to have Devel module test node access permissions. As it states here, this can cause significant performance overhead. So for now, even on our development site, let's leave this unchecked. If we want to check the node access debug, we can come back and enable it later.
16. Use the Standard drupal error handler. Backtrace will give you a nicer display of your debug information, but you'll need to install the Krumo library in order to use this.
a Administration menu settings
Display additional data for each menu item:
Menu link ID <" Weight <~ Parent link ID
Display the selected items next to each menu item link.
D Display all menu items
If enabled, all menu items are displayed regardless of your site permissions. Note: Do not e/iable o.n a production sits.
H Devel Node Access debug mode
Debug mode verifies the grants in the node_access table against those that would be set by running [Rebuild permiss considerable overhead.
© Default f Log only
© Standard drupal © Backtrace
Choose an error handler for your site, Backtrace prints nice debug information when an error is noticed, and you choosi krumo library. IV&ne is a good option vihen stepping through the site in your debugger.
17. Save configuration.
Was this article helpful?