열 기반 엔진은 채우기, 새로고침, 추천과 같은 백그라운드 유지관리 작업에 CPU 코어의 최대 20% 를 사용합니다. 유지보수 작업을 허용하도록 CPU 리소스를 조정하려면 google_job_scheduler.maintenance_cpu_percentage 플래그를 20~100 사이의 값으로 설정합니다. 기본값은 20입니다. 백그라운드 유지관리 작업의 최저 CPU 사용률은 1vCPU입니다.
열 기반 엔진은 채우기 및 새로고침 백그라운드 작업에 최대 2개의 작업자 프로세스를 사용합니다. 이러한 작업의 속도를 높이려면 다음 플래그를 설정하여 백그라운드 작업의 작업자 프로세스 수를 늘리세요. 기본 설정은 작업자 프로세스 2개입니다. 이러한 프로세스는 google_job_scheduler.maintenance_cpu_percentage 플래그에 지정된 제한된 CPU 리소스에서 실행됩니다. 이 플래그는 데이터베이스를 다시 시작할 필요가 없습니다.
예상되는 스캔 중심 워크로드에 따라 google_columnar_engine.auto_columnarization_schedule 플래그에서 자동 열 형식화 일정을 설정할 수 있습니다. 이 플래그에 대해 1시간 이상을 지정합니다. 이 플래그의 값을 변경해도 데이터베이스를 다시 시작할 필요가 없습니다.
열 기반 엔진을 수동으로 채우기
이 예시에서는 열 형식 엔진을 수동으로만 채울 수 있습니다.
google_columnar_engine.enable_auto_columnarization = OFF
열 형식 엔진을 수동으로만 채우려면 google_columnar_engine.enable_auto_columnarization 플래그를 OFF로 설정하세요. 기본적으로 플래그는 ON로 설정됩니다. 이 플래그의 값을 변경해도 데이터베이스를 다시 시작할 필요가 없습니다.
자세한 내용은 콘텐츠 수동 관리 섹션을 참고하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-05(UTC)"],[[["\u003cp\u003eThe \u003ccode\u003egoogle_job_scheduler.maintenance_cpu_percentage\u003c/code\u003e flag can be adjusted to allocate between 20% and 100% of CPU cores for columnar engine maintenance tasks, with the default set at 20%.\u003c/p\u003e\n"],["\u003cp\u003eTo speed up columnar engine operations, you can increase the number of worker processes by modifying the \u003ccode\u003egoogle_job_scheduler.max_parallel_workers_per_job\u003c/code\u003e flag, which defaults to 2.\u003c/p\u003e\n"],["\u003cp\u003eThe frequency of auto-columnarization can be customized by setting the \u003ccode\u003egoogle_columnar_engine.auto_columnarization_schedule\u003c/code\u003e flag to specify how often (in hours) it should run.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003egoogle_columnar_engine.enable_auto_columnarization\u003c/code\u003e flag can be set to \u003ccode\u003eOFF\u003c/code\u003e if you prefer to manually manage the columnar engine population, instead of the default \u003ccode\u003eON\u003c/code\u003e for auto-population.\u003c/p\u003e\n"]]],[],null,["# Tune the columnar engine for AlloyDB Omni on a VM\n\nSelect a documentation version: Current (16.8.0)keyboard_arrow_down\n\n- [Current (16.8.0)](/alloydb/omni/current/docs/columnar-engine/tune-columnar-engine)\n- [16.8.0](/alloydb/omni/16.8.0/docs/columnar-engine/tune-columnar-engine)\n- [16.3.0](/alloydb/omni/16.3.0/docs/columnar-engine/tune-columnar-engine)\n- [15.12.0](/alloydb/omni/15.12.0/docs/columnar-engine/tune-columnar-engine)\n- [15.7.1](/alloydb/omni/15.7.1/docs/columnar-engine/tune-columnar-engine)\n- [15.7.0](/alloydb/omni/15.7.0/docs/columnar-engine/tune-columnar-engine)\n\n\u003cbr /\u003e\n\nThis document describes how to tune the columnar engine for an AlloyDB Omni on a VM. This document assumes that you are familiar with PostgreSQL.\n\n\u003cbr /\u003e\n\n### Adjust the CPU resources for maintenance tasks\n\nThis example configures the columnar engine to use 50% of the CPU cores. \n\n google_job_scheduler.maintenance_cpu_percentage = 50\n\nColumnar engine uses up to 20% of CPU cores for background maintenance jobs, such as population, refresh, and recommendation. To adjust the CPU resources to allow for maintenance tasks, set the `google_job_scheduler.maintenance_cpu_percentage` flag to a value from 20 to 100. The default value is 20. The lowest CPU utilization for background maintenance tasks is 1 vCPU.\n\n### Increase the speed of worker processes\n\nThis example sets four worker processes. \n\n google_job_scheduler.max_parallel_workers_per_job = 4\n\nThe columnar engine uses up to two worker processes for population and refresh background jobs. To increase the speed of these operations, set the following flag to increase the number of worker processes for background jobs. The default setting is 2 worker processes. These processes run on limited CPU resources as specified in the `google_job_scheduler.maintenance_cpu_percentage` flag. This flag does not require the database to be restarted.\n\n### Change the auto-columnarization schedule\n\nThis example sets the auto-columnarization schedule to six hours. \n\n google_columnar_engine.auto_columnarization_schedule = 'EVERY 6 HOURS'\n\nThe auto-columnarization schedule can be set in the `google_columnar_engine.auto_columnarization_schedule` flag based upon anticipated scan-heavy workloads. Specify one or more hours for this flag. Changing the value of this flag does not require a database restart.\n\n### Manually populate the columnar engine\n\nThis example lets you only manually populate the columnar engine. \n\n google_columnar_engine.enable_auto_columnarization = OFF\n\nIf you prefer to only manually populate the columnar engine, set the `google_columnar_engine.enable_auto_columnarization` flag to `OFF`. By default, the flag is set to `ON`. Changing the value of this flag does not require a database restart.\nSee [Manage Content Manually](/alloydb/omni/current/docs/columnar-engine/manage-content-manually) section for more details."]]
