Reference documentation and code samples for the Cloud Profiler V2 API module Google::Cloud::Profiler::V2::ProfileType.
ProfileType is type of profiling data.
NOTE: the enumeration member names are used (in lowercase) as unique string
identifiers of profile types, so they must not be renamed.
Constants
PROFILE_TYPE_UNSPECIFIED
value: 0 Unspecified profile type.
CPU
value: 1 Thread CPU time sampling.
WALL
value: 2 Wallclock time sampling. More expensive as stops all threads.
HEAP
value: 3 In-use heap profile. Represents a snapshot of the allocations that are
live at the time of the profiling.
THREADS
value: 4 Single-shot collection of all thread stacks.
CONTENTION
value: 5 Synchronization contention profile.
PEAK_HEAP
value: 6 Peak heap profile.
HEAP_ALLOC
value: 7 Heap allocation profile. It represents the aggregation of all allocations
made over the duration of the profile. All allocations are included,
including those that might have been freed by the end of the profiling
interval. The profile is in particular useful for garbage collecting
languages to understand which parts of the code create most of the garbage
collection pressure to see if those can be optimized.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-09 UTC."],[],[],null,["# Cloud Profiler V2 API - Module Google::Cloud::Profiler::V2::ProfileType (v1.3.0)\n\nVersion latestkeyboard_arrow_down\n\n- [1.3.0 (latest)](/ruby/docs/reference/google-cloud-profiler-v2/latest/Google-Cloud-Profiler-V2-ProfileType)\n- [1.2.1](/ruby/docs/reference/google-cloud-profiler-v2/1.2.1/Google-Cloud-Profiler-V2-ProfileType)\n- [1.1.0](/ruby/docs/reference/google-cloud-profiler-v2/1.1.0/Google-Cloud-Profiler-V2-ProfileType)\n- [1.0.1](/ruby/docs/reference/google-cloud-profiler-v2/1.0.1/Google-Cloud-Profiler-V2-ProfileType)\n- [0.10.1](/ruby/docs/reference/google-cloud-profiler-v2/0.10.1/Google-Cloud-Profiler-V2-ProfileType)\n- [0.9.2](/ruby/docs/reference/google-cloud-profiler-v2/0.9.2/Google-Cloud-Profiler-V2-ProfileType)\n- [0.8.0](/ruby/docs/reference/google-cloud-profiler-v2/0.8.0/Google-Cloud-Profiler-V2-ProfileType)\n- [0.7.0](/ruby/docs/reference/google-cloud-profiler-v2/0.7.0/Google-Cloud-Profiler-V2-ProfileType)\n- [0.6.1](/ruby/docs/reference/google-cloud-profiler-v2/0.6.1/Google-Cloud-Profiler-V2-ProfileType)\n- [0.5.0](/ruby/docs/reference/google-cloud-profiler-v2/0.5.0/Google-Cloud-Profiler-V2-ProfileType)\n- [0.4.0](/ruby/docs/reference/google-cloud-profiler-v2/0.4.0/Google-Cloud-Profiler-V2-ProfileType)\n- [0.3.0](/ruby/docs/reference/google-cloud-profiler-v2/0.3.0/Google-Cloud-Profiler-V2-ProfileType)\n- [0.2.5](/ruby/docs/reference/google-cloud-profiler-v2/0.2.5/Google-Cloud-Profiler-V2-ProfileType) \nReference documentation and code samples for the Cloud Profiler V2 API module Google::Cloud::Profiler::V2::ProfileType.\n\nProfileType is type of profiling data.\nNOTE: the enumeration member names are used (in lowercase) as unique string\nidentifiers of profile types, so they must not be renamed.\n\nConstants\n---------\n\n### PROFILE_TYPE_UNSPECIFIED\n\n**value:** 0 \nUnspecified profile type.\n\n### CPU\n\n**value:** 1 \nThread CPU time sampling.\n\n### WALL\n\n**value:** 2 \nWallclock time sampling. More expensive as stops all threads.\n\n### HEAP\n\n**value:** 3 \nIn-use heap profile. Represents a snapshot of the allocations that are\nlive at the time of the profiling.\n\n### THREADS\n\n**value:** 4 \nSingle-shot collection of all thread stacks.\n\n### CONTENTION\n\n**value:** 5 \nSynchronization contention profile.\n\n### PEAK_HEAP\n\n**value:** 6 \nPeak heap profile.\n\n### HEAP_ALLOC\n\n**value:** 7 \nHeap allocation profile. It represents the aggregation of all allocations\nmade over the duration of the profile. All allocations are included,\nincluding those that might have been freed by the end of the profiling\ninterval. The profile is in particular useful for garbage collecting\nlanguages to understand which parts of the code create most of the garbage\ncollection pressure to see if those can be optimized."]]
