the system does not limit the number of processors, you can do so if desired by setting NumCPUs  (also added in NDB 8.0.23). Otherwise, automatic thread configuration accommodates up to 1024 CPUs. 

Automatic thread configuration occurs regardless of any values set for ThreadConfig  or MaxNoOfExecutionThreads  in config.ini ; this means that it is not necessary to set either of these parameters. 

In addition, NDB 8.0.23 implements a number of new ndbinfo  information database tables providing information about hardware and CPU availability, as well as CPU usage by NDB  data nodes. These tables are listed here: 

• cpudata 

• cpudata_1sec 

• cpudata_20sec 

• cpudata_50ms 

• cpuinfo 

• hwinfo 

Some of these tables are not available on every platform supported by NDB Cluster; see the individual descriptions of them for more information. 

• Hierachical views of NDB database objects.  The dict_obj_tree  table, added to the ndbinfo information database in NDB 8.0.24, can provide hierarchical and tree-like views of many NDB  database objects, including the following: 

•Tables and associated indexes 

•Tablespaces and associated data files 

•Logfile groups and associated undo log files 

For more information and examples, see Section 23.5.14.22, “The ndbinfo dict_obj_tree Table” . 

• Index statistics enhancements.  NDB 8.0.24 implements the following improvements in calculation of index statistics: 

•Index statistics were previously collected from one fragment only; this is changed such that this extrapolation is extended to additional fragments. 

•The algorithm used for very small tables, such as those having very few rows where results are discarded, has been improved, so that estimates for such tables should be more accurate than previously. 

For additional information, see Section 23.5.13, “NDB API Statistics Counters and Variables” . 

• Conversion between NULL and NOT NULL during restore operations.  Beginning with NDB 8.0.26, ndb_restore  can support restoring of NULL  columns as NOT NULL  and the reverse, using the options listed here: 

•To restore a NULL  column as NOT NULL , use the --lossy-conversions  option. 

The column originally declared as NULL  must not contain any NULL  rows; if it does, ndb_restore exits with an error. 

