Configuring the Profile Log Service

Table of Contents

Profile Log Service Defaults

Need help?

Schedule a consultation with an Azul performance expert.

When you use the Cloud Native Compiler Profile Log Service, JVMs all write profile log candidates to unique profile names on the service. CNC gathers all of the candidates for a profile name and decides which is th best candidate to serve to JVM clients requesting that profile name.

When considering what settings are set on the client versus on the service:

Individual JVMs decide when CNC should consider their profile log is a suitable candidate for sharing with other JVMs. They can also override server-side defaults for profile log nomination candidates and maximum profile log size.
CNC also controls the rules for where to store ReadyNow profile logs, when to clean up old logs, and service-wide defaults for profile log candidate nomination and maximum profile log size.

Profile Log Service Defaults

CNC admins can set the following global defaults for ReadyNow profiles:

Option	Description	Default
persistentprofile.storage-service	Decide back-end storage. Only s3 is supported at the moment	s3
persistentprofile.bucket	Name of the s3 bucket to use for storage	persistent-profile
persistentprofile.debug-info-history-length	Limit of rolling profile history entries	100
persistentprofile.cache.enabled	Enabling of caching the chunk content on the gateway	false
persistentprofile.producers.max-concurrent-recordings	The number of concurrent copies of a specific generation CNC will accept before it tells other JVMs trying to write the same generation of the same Profile Name to stop	5
persistentprofile.producers.max-promotable-generation	Maximum number of generations CNC will accept for a Profile Name. Note that here is no 'unlimited' value available	3
persistentprofile.producers.max-profile-size	Limit on the input profile size, in bytes. No limit by default	0
persistentprofile.cleaner.enabled	Enabling of automatic repository clean-up	false
persistentprofile.cleaner.target-size	Target amount of data stored in the repository, in bytes	0
persistentprofile.cleaner.warning-size	Warning amount of data stored in the repository, in bytes	0

Option

Description

Default

persistentprofile.storage-service

Decide back-end storage. Only s3 is supported at the moment

persistentprofile.bucket

Name of the s3 bucket to use for storage

persistent-profile

persistentprofile.debug-info-history-length

Limit of rolling profile history entries

100

persistentprofile.cache.enabled

Enabling of caching the chunk content on the gateway

false

persistentprofile.producers.max-concurrent-recordings

The number of concurrent copies of a specific generation CNC will accept before it tells other JVMs trying to write the same generation of the same Profile Name to stop

persistentprofile.producers.max-promotable-generation

Maximum number of generations CNC will accept for a Profile Name. Note that here is no 'unlimited' value available

persistentprofile.producers.max-profile-size

Limit on the input profile size, in bytes. No limit by default

persistentprofile.cleaner.enabled

Enabling of automatic repository clean-up

false

persistentprofile.cleaner.target-size

Target amount of data stored in the repository, in bytes

persistentprofile.cleaner.warning-size

Warning amount of data stored in the repository, in bytes

Note	To disable Compilation Service altogether on the CNC service and only use CNC for Profile Log Service, set `compilations.parallelism.limitPerVm` to 0.