WRENCH
1.11
Cyberinfrastructure Simulation Workbench
|
Overview | Installation | Getting Started | WRENCH 101 | WRENCH 102 |
A batch_standard_and_pilot_jobs-scheduled compute service that manages a set of compute hosts and controls access to their resource via a batch_standard_and_pilot_jobs queue. More...
#include <BatchComputeService.h>
Public Member Functions | |
BatchComputeService (const std::string &hostname, std::vector< std::string > compute_hosts, std::string scratch_space_mount_point, WRENCH_PROPERTY_COLLECTION_TYPE property_list={}, WRENCH_MESSAGE_PAYLOADCOLLECTION_TYPE messagepayload_list={}) | |
Constructor. More... | |
bool | supportsCompoundJobs () override |
Returns true if the service supports compound jobs. More... | |
bool | supportsPilotJobs () override |
Returns true if the service supports pilot jobs. More... | |
bool | supportsStandardJobs () override |
Returns true if the service supports standard jobs. More... | |
Additional Inherited Members | |
Static Public Attributes inherited from wrench::ComputeService | |
static constexpr unsigned long | ALL_CORES = ULONG_MAX |
A convenient constant to mean "use all cores of a physical host" whenever a number of cores is needed when instantiating compute services. | |
static constexpr double | ALL_RAM = DBL_MAX |
A convenient constant to mean "use all ram of a physical host" whenever a ram capacity is needed when instantiating compute services. | |
A batch_standard_and_pilot_jobs-scheduled compute service that manages a set of compute hosts and controls access to their resource via a batch_standard_and_pilot_jobs queue.
In the current implementation of this service, like for many of its real-world counterparts, memory_manager_service partitioning among jobs onq the same host is not handled. When multiple jobs share hosts, which can happen when jobs require only a few cores per host and can thus be co-located on the same hosts in a non-exclusive fashion, each job simply runs as if it had access to the full RAM of each compute host it is scheduled on. The simulation of these memory_manager_service contended scenarios is thus, for now, not realistic as there is no simulation of the effects of memory_manager_service sharing (e.g., swapping).
wrench::BatchComputeService::BatchComputeService | ( | const std::string & | hostname, |
std::vector< std::string > | compute_hosts, | ||
std::string | scratch_space_mount_point, | ||
WRENCH_PROPERTY_COLLECTION_TYPE | property_list = {} , |
||
WRENCH_MESSAGE_PAYLOADCOLLECTION_TYPE | messagepayload_list = {} |
||
) |
Constructor.
hostname | the hostname on which to start the service |
compute_hosts | the list of names of the available compute hosts
|
scratch_space_mount_point | the mount point of the scratch storage space for the service ("" means "no scratch space") |
property_list | a property list that specifies BatchComputeServiceProperty values ({} means "use all defaults") |
messagepayload_list | a message payload list that specifies BatchComputeServiceMessagePayload values ({} means "use all defaults") |
|
override |
Returns true if the service supports compound jobs.
|
override |
Returns true if the service supports pilot jobs.
|
override |
Returns true if the service supports standard jobs.