Some performance tweak

CMakeLists.txt

@@ -100,7 +100,7 @@ if(LIBCOSIM_USING_CONAN)
     endif()
 endif()
 
-set(Boost_components date_time fiber log)
+set(Boost_components date_time log)
 if (LIBCOSIM_BUILD_TESTS)
     list(APPEND Boost_components timer unit_test_framework)
 endif()

docs/main_page.md

@@ -56,7 +56,7 @@ By far, the easiest way to set up an execution is to first create a
 `cosim::system_structure`, as described above, and inject this structure
 into an empty `cosim::execution` using `cosim::inject_system_structure()`.
 However, it is also possible to build the execution "by hand" by adding
-simulators and functions to it in the form of `cosim::async_slave` and
+simulators and functions to it in the form of `cosim::slave` and
 `cosim::function` objects, respectively.
 
 When would you choose which method? Starting with `cosim::system_structure`
@@ -156,7 +156,7 @@ completeness and ease of reference:
   * `cosim::algorithm` – to implement alternative co-simulation algorithms
   * `cosim::observer` – to implement your own observers
   * `cosim::manipulator` – to implement your own manipulators
-  * `cosim::model`, `cosim::async_slave` and `cosim::slave` – to implement
+  * `cosim::model` and `cosim::slave` – to implement
     simulators that don't necessarily come in the form of FMUs
   * `cosim::function_type` and `cosim::function` – to implement additional
     function types

include/cosim/algorithm/fixed_step_algorithm.hpp

@@ -30,8 +30,11 @@ class fixed_step_algorithm : public algorithm
      *
      *  \param baseStepSize
      *      The base communication interval length.
+     *
+     *  \param workerThreadCount
+     *      A number of worker threads to spawn for running FMUs
      */
-    explicit fixed_step_algorithm(duration baseStepSize);
+    explicit fixed_step_algorithm(duration baseStepSize, std::optional<unsigned int> workerThreadCount = std::nullopt);
 
     ~fixed_step_algorithm() noexcept;
 

include/cosim/algorithm/simulator.hpp

@@ -14,8 +14,6 @@
 #include <cosim/model_description.hpp>
 #include <cosim/time.hpp>
 
-#include <boost/fiber/future.hpp>
-
 #include <functional>
 #include <optional>
 #include <string_view>
@@ -29,14 +27,6 @@ namespace cosim
  *
  *  This is the simulator interface exposed to `algorithm` implementers,
  *  and is used to control one "sub-simulator" in a co-simulation.
- *
- *  Some of the functions in this class, specifically the ones that return a
- *  `boost::fibers::future` object, are asynchronous.  Only one asynchronous
- *  operation may be executed per `simulator` object at any given time,
- *  meaning that client code must *always* ensure that the previous operation
- *  has completed before starting a new one. This is typically done by calling
- *  `boost::fibers::future::get()` on the future returned from the previous
- *  function call.
  */
 class simulator : public manipulable
 {
@@ -91,7 +81,7 @@ class simulator : public manipulable
      *      solver doesn't use error estimation, it will just ignore this
      *      parameter.
      */
-    virtual boost::fibers::future<void> setup(
+    virtual void setup(
         time_point startTime,
         std::optional<time_point> stopTime,
         std::optional<double> relativeTolerance) = 0;
@@ -118,7 +108,7 @@ class simulator : public manipulable
      *  propagate initial values between simulators and/or bring the system
      *  to a steady state.
      */
-    virtual boost::fibers::future<void> do_iteration() = 0;
+    virtual void do_iteration() = 0;
 
     /**
      *  Signals to the simulator that the initialization phase is complete
@@ -127,7 +117,7 @@ class simulator : public manipulable
      *  This function must be called at the end of the initialisation phase,
      *  after any call to `do_iteration()` and before the first `do_step()` call.
      */
-    virtual boost::fibers::future<void> start_simulation() = 0;
+    virtual void start_simulation() = 0;
 
     /**
      *  Performs a single time step.
@@ -140,7 +130,7 @@ class simulator : public manipulable
      *  \param deltaT
      *      The length of the time step. Must be positive.
      */
-    virtual boost::fibers::future<step_result> do_step(
+    virtual step_result do_step(
         time_point currentT,
         duration deltaT) = 0;
 };