Reduce Number of SQL Calls By Storing Breakpoints in Memory

Committed and pushed to dev version, can somebody test it so I can make a release

+++ b/breakpoints.module
@@ -360,15 +363,26 @@ function breakpoints_breakpoint_load($name, $source, $source_type) {
+  $breakpoints = &drupal_static(__FUNCTION__, NULL);

The places that are now calling cache_clear_all() are not calling drupal_static_reset() so this function will contain stale data until the next request.

Overall I feel like this is odd knowing that CTools itself also uses database caching, and rather than storing in yet-another-database-cache, just adding static caching, and loading them all at once from CTools would be the primary improvement.

Yes, we just have to enable 'cache defaults' as per the CTools export documentation.

Hrm, so the caching is for the default exported objects, so it skips invoking the hooks, but still requires one database read on loading either all breakpoints or all groups for reading from the table itself.

This gets me down to loading from the cache table only for both breakpoints and breakpoint groups. Abstract cache clearing to separate functions for re-use, and takes advantage of the 'load all callback' to help centralize caching.

Missed that $bin parameter to cache_clear_all() is required if using a specific $cid parameter.

Committed to dev