Add a quick and dirty performance test program

src/communication/export_manager.hpp

@@ -47,6 +47,8 @@ public:
 
     void do_export_rank(const std::vector<spike_type>& spikes)
     {
+        // TODO: do the buffering of the spikes here and not in the 
+        //      exporters itself!!!
         for (auto &exporter : rank_exporters_)
         {
             exporter->add_and_export(spikes);

src/model.hpp

@@ -137,7 +137,7 @@ public:
                 auto local_spikes = previous_spikes().gather();
                 future_events() = communicator_.exchange(local_spikes,
                     [&](const std::vector<spike_type>& spikes) { exporter_->do_export_rank(spikes); },
-                [&] (const std::vector<spike_type>& spikes){ exporter_->do_export_single(spikes); });
+                    [&] (const std::vector<spike_type>& spikes){ exporter_->do_export_single(spikes); });
                 PL(2);
             };
 

tests/CMakeLists.txt

@@ -14,6 +14,9 @@ add_subdirectory(validation)
 # Test for the internode communication (eg. mpi)
 add_subdirectory(global_communication)
 
+# Tests for performance: This could include stand alone tests. These do not necessarily be run automatically
+add_subdirectory(performance)
+
 
 # Proposed additional test types:
 
@@ -21,7 +24,6 @@ add_subdirectory(global_communication)
 
 # Test to check integration between components 
 
-# Tests for performance: This could include stand alone tests. These do not necessarily be run automatically
 
 # Numbered tests based on bugs in the tracker