<commit_before># The different vendors. Using a vendor different Datagrids can be tested.
#
# Options currently are:
# hazelcast4
# hazelcast-enterprise4
# hazelcast3
# hazelcast-enterprise3
# ignite2
# infinispan9
# couchbase
# lettuce5
# lettucecluster5
# jedis3
#
VENDOR=hazelcast4

# =============================================================================
# Cloud selection
# =============================================================================
#
# Currently configured for EC2, but can also be something else:
# local = statically configured to run on the local machine.
# static = statically configured set of machines.
# aws-ec2 = Amazon EC2
# google-compute-engine = The Google Compute Engine.

#
# If you are using aws-ec, make sure the SUBNET_ID and PLACEMENT_GROUP
# are set for better performance.
#
CLOUD_PROVIDER=local

# =============================================================================
# Cloud credentials
# =============================================================================
#
# The cloud identity (AWS access key ID).
#
# The cloud identity can be configured in two was:
#    1: using a file reference. So you set the path to the file containing the
#       cloud identity. This is the preferred way because it is more secure.
#       Normally you put this file in your home dir
#    2: using the value. This is the simplest way, but you need to be careful
#       that this doesn't leave your system. E.g. because it got added to a
# git repo, zipped etc.
#
#
CLOUD_IDENTITY=~/ec2.identity

#
# The cloud credential (AWS secret access key).
#
# It can be configured in the same way as CLOUD_IDENTITY using direct value or
# file reference.
#
CLOUD_CREDENTIAL=~/ec2.credential

#
# Just a prefix for the agent name. Different test clusters could be given
# different names. In GCE you need to be very careful using multiple
# executionGroup-names, because for every port and every executionGroup-name a
# firewall rule is made and you can only have 100 firewall rules.
#
# If the name contains ${username}, this section will be replaced by the actual
# user that runs the test. This makes it very easy to identity which user is
# owning a certain machine.
#
GROUP_NAME=simulator-agent-${username}

#
# The name of the SIMULATOR_USER on remote machines
#
# The default value 'simulator' is fine in most cases. So probably you don't
# want to change this.
#
SIMULATOR_USER=simulator

#
# The options added to SSH. Probably you don't need to change this.
#
SSH_OPTIONS=-o BatchMode=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null

#
# The name of the security group, the creates machines belong to.
#
# EC2:
# If the security group doesn't exist, it will automatically be created. If you
# did not specify a locationId in the MACHINES_SPEC, the location will be us-east-1.
# If it does exist, make sure that port 22, 9000, 9001 and 5701..5751 are open.
# In most cases the default value is fine.
#
# Others:
# The value is not relevant.
SECURITY_GROUP=simulator

#
# EC2:
# You can specify VPC subnet ID. If SUBNET_ID is different than 'default' then
# machines are created in EC2 VPC and the SECURITY_GROUP option is ignored.
#
# Check the following link to define a VPC:
# https://console.aws.amazon.com/vpc
#
# SUBNET_ID has to exist before it's used.
#
# GCE:
# The value is not relevant
#
# Example 'SUBNET_ID=subnet-378d2140'
#
SUBNET_ID=default

# EC2:
# You can specify extra arguments to the `aws ec2 run-instances` create command
#
# Example:
# EC2_RUN_INSTANCE_ARGS=--placement {\"GroupName\":\"simulator\",\"Tenancy\":\"dedicated\"}
EC2_RUN_INSTANCE_ARGS=default

#
# A placement group is a logical grouping for cluster instances. Placement groups
# have a low latency, full bisection 20 Gbps bandwidth between instances
#
# Example 'PLACEMENT_GROUP=simulator'
#
# Set this when more reliable performance is required.
#
# The following placement groups are available
# simulator (cluster placement group)
# simulator-spread (spread placement group)
# simulator-partition (partition placement group)
#
# Don't combine this setting with EC2_RUN_INSTANCE_ARGS
#
PLACEMENT_GROUP=default

#
# https://aws.amazon.com/ec2/spot/pricing/
#
#EC2_SPOT_PRICE=0.3

REGION=us-east-1

#
# The id of the image to use.
#
# This is the default: Amazon Linux 2 AMI (HVM),
#
IMAGE_ID=ami-0fc61db8544a617ed

# For a listing of ec2 instance types:
# https://aws.amazon.com/ec2/instance-types/
# http://www.ec2instances.info/
INSTANCE_TYPE=c5.2xlarge

# =============================================================================
# Hazelcast Version Configuration
# =============================================================================
#
# The workers can be configured to use a specific version of Hazelcast; so
# you don't need to depend on the Hazelcast version provided by the simulator,
# but you can override it with a specific version.
#
# The Hazelcast version can be configured in different ways:
#   outofthebox             : if you are fine with the one provided by the
#                             Simulator itself.
#   maven=version           : if you want to use a specific version from the maven
#                             repository, e.g.
#                                   maven=4.0
#                                   maven=4.1-SNAPSHOT
#                             Local Hazelcast artifacts will be preferred, so you
#                             can checkout e.g. an experimental branch, build the
#                             artifacts locally. This will all be done on the local
#                             machine, not
#                             on the agent machine.
#   bringmyown              : if you want to bring your own dependencies. To upload your
#                             dependencies, in the working dir, create an 'upload'
#                             directory. The content of this directory will be
#                             uploaded to the agents and automatically
#   added to the classpath of the workers.
#   git=version             : if you want Simulator to use a specific version of
#                             Hazelcast from Git, e.g.:
#                                   git=f0288f713    to build a specific revision
#                                   git=v3.2.3       to build a version from a Git tag
#                                   git=myRepository/myBranch - to build a version
#                                   from a branch in a specific repository.
#   Use GIT_CUSTOM_REPOSITORIES to specify custom repositories. The main Hazelcast
#                             repository is always named "origin".
#
VERSION_SPEC=outofthebox

# When HAZELCAST_VERSION_SPEC is set to Git then it will download Hazelcast
# sources to this directory.
#
GIT_BUILD_DIR=~/.hazelcast-build/

# Comma separated list of additional Git repositories to be fetched when
# HAZELCAST_VERSION_SPEC is set to Git.
#
# Simulator will always fetch https://github.com/hazelcast/hazelcast
# This property specifies additional repositories. You can use both remote and
# local repositories. Remote repositories must be accessible for anonymous,
# local repositories must be accessible for current user.
#
# Default value: empty, only the main Hazelcast repository is used by default.
#
#GIT_CUSTOM_REPOSITORIES=myFork=https://github.com/jerrinot/hazelcast.git,localRepo=/home/jara/devel/oss/hazelcast

# Path to a local Maven installation to use when HAZELCAST_VERSION_SPEC is
# set to Git.
#
# Default value: Simulator expects 'mvn' binary to be available on a PATH.
#
#MVN_EXECUTABLE=/usr/bin/mvn

# =============================================================================
# JDK Installation
# =============================================================================
#
# JDK installation for machines provisioned in the cloud. Is ignored
# for static environments.
#
# Warning: there is only support for 64 bit X86 JVMs.
#
# The following 4 flavors are available:
#   ibm
#   oracle
#   openjdk
#   zulu
#   outofthebox
#
# "outofthebox" is the Java version provided by the image, so no software is
# installed by Hazelcast Simulator. If you want to use e.g. ARM or something
# else that isn't X86-64, set the value to 'outofthebox' and take care
# of the installation yourself. E.g. using agent-ssh 'sudo yum -y install whatever'
#
# If you want to use openjdk, it is best to use zulu since it is just an
# openjdk distribution. The installation is more reliable and more versions
# are supported.
#
JDK_FLAVOR=oracle

#
# The version of Java to install.
#
# IBM supports 8/9 (9 is an early access version)
# OpenJDK supports 8/9/10/11/13/14/15
# Oracle supports 8/9/11/13
# Zulu:
#   If the version is an integer, then the following versions are supported.
#       8/9/10/11
#   This style is deprecated because you have no control on the version (could be very stale)
#
#   If the version is not an integer, it will be interpreted as a specific version.
#       You can get a list of available versions here:
#       https://cdn.azul.com/zulu/bin/
#       An example:
#       VERSION=zulu8.12.0.1-jdk8.0.71-linux_x64.tar.gz
#       Keep in mind that you need to select a linux x86 JDK (JRE is not sufficient)
#
# When using Java 9+, add the following to the jvm arguments
# '--add-modules java.xml.bind'. Otherwise you will get a
# 'java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter'
#
# Versions before Java 8 are not supported because Simulator requires 8+<commit_msg>Minor documentation fix<commit_after># The different vendors. Using a vendor different Datagrids can be tested.
#
# Options currently are:
# hazelcast4
# hazelcast-enterprise4
# hazelcast3
# hazelcast-enterprise3
# ignite2
# infinispan9
# couchbase
# lettuce5
# lettucecluster5
# jedis3
#
VENDOR=hazelcast4

# =============================================================================
# Cloud selection
# =============================================================================
#
# Currently configured for EC2, but can also be something else:
# local = statically configured to run on the local machine.
# static = statically configured set of machines.
# aws-ec2 = Amazon EC2
# google-compute-engine = The Google Compute Engine.

#
# If you are using aws-ec, make sure the SUBNET_ID and PLACEMENT_GROUP
# are set for better performance.
#
CLOUD_PROVIDER=local

# =============================================================================
# Cloud credentials
# =============================================================================
#
# The cloud identity (AWS access key ID).
#
# The cloud identity can be configured in two was:
#    1: using a file reference. So you set the path to the file containing the
#       cloud identity. This is the preferred way because it is more secure.
#       Normally you put this file in your home dir
#    2: using the value. This is the simplest way, but you need to be careful
#       that this doesn't leave your system. E.g. because it got added to a
# git repo, zipped etc.
#
#
CLOUD_IDENTITY=~/ec2.identity

#
# The cloud credential (AWS secret access key).
#
# It can be configured in the same way as CLOUD_IDENTITY using direct value or
# file reference.
#
CLOUD_CREDENTIAL=~/ec2.credential

#
# Just a prefix for the agent name. Different test clusters could be given
# different names. In GCE you need to be very careful using multiple
# executionGroup-names, because for every port and every executionGroup-name a
# firewall rule is made and you can only have 100 firewall rules.
#
# If the name contains ${username}, this section will be replaced by the actual
# user that runs the test. This makes it very easy to identity which user is
# owning a certain machine.
#
GROUP_NAME=simulator-agent-${username}

#
# The name of the SIMULATOR_USER on remote machines
#
# The default value 'simulator' is fine in most cases. So probably you don't
# want to change this.
#
SIMULATOR_USER=simulator

#
# The options added to SSH. Probably you don't need to change this.
#
SSH_OPTIONS=-o BatchMode=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null

#
# The name of the security group, the creates machines belong to.
#
# EC2:
# If the security group doesn't exist, it will automatically be created. If you
# did not specify a locationId in the MACHINES_SPEC, the location will be us-east-1.
# If it does exist, make sure that port 22, 9000, 9001 and 5701..5751 are open.
# In most cases the default value is fine.
#
# Others:
# The value is not relevant.
SECURITY_GROUP=simulator

#
# EC2:
# You can specify VPC subnet ID. If SUBNET_ID is different than 'default' then
# machines are created in EC2 VPC and the SECURITY_GROUP option is ignored.
#
# Check the following link to define a VPC:
# https://console.aws.amazon.com/vpc
#
# SUBNET_ID has to exist before it's used.
#
# GCE:
# The value is not relevant
#
# Example 'SUBNET_ID=subnet-378d2140'
#
SUBNET_ID=default

# EC2:
# You can specify extra arguments to the `aws ec2 run-instances` create command
#
# Example:
# EC2_RUN_INSTANCE_ARGS=--placement {\"GroupName\":\"simulator\",\"Tenancy\":\"dedicated\"}
EC2_RUN_INSTANCE_ARGS=default

#
# A placement group is a logical grouping for cluster instances. Placement groups
# have a low latency, full bisection 20 Gbps bandwidth between instances
#
# Example 'PLACEMENT_GROUP=simulator'
#
# Set this when more reliable performance is required.
#
# The following placement groups are available
# simulator (cluster placement group)
# simulator-spread (spread placement group)
# simulator-partition (partition placement group)
#
# Don't combine this setting with EC2_RUN_INSTANCE_ARGS
#
PLACEMENT_GROUP=default

#
# https://aws.amazon.com/ec2/spot/pricing/
#
#EC2_SPOT_PRICE=0.3

REGION=us-east-1

#
# The id of the image to use.
#
# This is the default: Amazon Linux 2 AMI (HVM),
#
IMAGE_ID=ami-0fc61db8544a617ed

# For a listing of ec2 instance types:
# https://aws.amazon.com/ec2/instance-types/
# http://www.ec2instances.info/
INSTANCE_TYPE=c5.2xlarge

# =============================================================================
# Hazelcast Version Configuration
# =============================================================================
#
# The workers can be configured to use a specific version of Hazelcast; so
# you don't need to depend on the Hazelcast version provided by the simulator,
# but you can override it with a specific version.
#
# The Hazelcast version can be configured in different ways:
#   outofthebox             : if you are fine with the one provided by the
#                             Simulator itself.
#   maven=version           : if you want to use a specific version from the maven
#                             repository, e.g.
#                                   maven=4.0
#                                   maven=4.1-SNAPSHOT
#                             Local Hazelcast artifacts will be preferred, so you
#                             can checkout e.g. an experimental branch, build the
#                             artifacts locally. This will all be done on the local
#                             machine, not
#                             on the agent machine.
#   bringmyown              : if you want to bring your own dependencies. To upload your
#                             dependencies, in the working dir, create an 'upload'
#                             directory. The content of this directory will be
#                             uploaded to the agents and automatically
#   added to the classpath of the workers.
#   git=version             : if you want Simulator to use a specific version of
#                             Hazelcast from Git, e.g.:
#                                   git=f0288f713    to build a specific revision
#                                   git=v3.2.3       to build a version from a Git tag
#                                   git=myRepository/myBranch - to build a version
#                                   from a branch in a specific repository.
#   Use GIT_CUSTOM_REPOSITORIES to specify custom repositories. The main Hazelcast
#                             repository is always named "origin".
#
VERSION_SPEC=outofthebox

# When HAZELCAST_VERSION_SPEC is set to Git then it will download Hazelcast
# sources to this directory.
#
GIT_BUILD_DIR=~/.hazelcast-build/

# Comma separated list of additional Git repositories to be fetched when
# HAZELCAST_VERSION_SPEC is set to Git.
#
# Simulator will always fetch https://github.com/hazelcast/hazelcast
# This property specifies additional repositories. You can use both remote and
# local repositories. Remote repositories must be accessible for anonymous,
# local repositories must be accessible for current user.
#
# Default value: empty, only the main Hazelcast repository is used by default.
#
#GIT_CUSTOM_REPOSITORIES=myFork=https://github.com/jerrinot/hazelcast.git,localRepo=/home/jara/devel/oss/hazelcast

# Path to a local Maven installation to use when HAZELCAST_VERSION_SPEC is
# set to Git.
#
# Default value: Simulator expects 'mvn' binary to be available on a PATH.
#
#MVN_EXECUTABLE=/usr/bin/mvn

# =============================================================================
# JDK Installation
# =============================================================================
#
# JDK installation for machines provisioned in the cloud. Is ignored
# for static environments.
#
# Warning: there is only support for 64 bit X86 JVMs.
#
# The following 4 flavors are available:
#   ibm
#   oracle
#   openjdk
#   zulu
#   outofthebox
#
# "outofthebox" is the Java version provided by the image, so no software is
# installed by Hazelcast Simulator. If you want to use e.g. ARM or something
# else that isn't X86-64, set the value to 'outofthebox' and take care
# of the installation yourself. E.g. using agent-ssh 'sudo yum -y install whatever'
#
# If you want to use openjdk, it is best to use zulu since it is just an
# openjdk distribution. The installation is more reliable and more versions
# are supported.
#
JDK_FLAVOR=oracle

#
# The version of Java to install.
#
# IBM supports 8/9 (9 is an early access version)
# OpenJDK supports 8/9/10/11/13/14/15
# Oracle supports 8/9/11/13
# Zulu:
#   If the version is an integer, then the following versions are supported.
#       8/9/10/11
#   This style is deprecated because you have no control on the version (could be very stale)
#
#   If the version is not an integer, it will be interpreted as a specific version.
#       You can get a list of available versions here:
#       https://cdn.azul.com/zulu/bin/
#       An example:
#       JDK_VERSION=zulu8.12.0.1-jdk8.0.71-linux_x64.tar.gz
#       Keep in mind that you need to select a linux x86 JDK (JRE is not sufficient)
#
# When using Java 9+, add the following to the jvm arguments
# '--add-modules java.xml.bind'. Otherwise you will get a
# 'java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter'
#
# Versions before Java 8 are not supported because Simulator requires 8+
{'fraction_non_alphanumeric': 0.13097363722298078, 'fraction_numerical': 0.01501943073206596, 'mean_word_length': 3.22708102108768, 'pattern_counts': {'":': 4, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 12, 'lorem ipsum': 0, 'www.': 2, 'xml': 4}, 'pii_count': 2, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 18, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6071773', 'n_tokens_mistral': 5515, 'n_tokens_neox': 5194, 'n_words': 2179}