 This page explains potential bottlenecks to be aware of when running CockroachDB in Kubernetes and shows you how to optimize your deployment for better performance.

Prerequisites

Before you focus on optimizing a Kubernetes-orchestrated CockroachDB cluster:

Verify that CockroachDB performs up to your requirements for your workload on identical hardware without Kubernetes. You may find that you need to modify your workload or use different machine specs to achieve the performance you need, and it's better to determine that up front than after spending a bunch of time trying to optimize your Kubernetes deployment.

Performance Factors

There are a number of independent factors that affect the performance you observe when running CockroachDB on Kubernetes. Some are more significant than others or easier to fix than others, so feel free to pick and choose the improvements that best fit your situation. Note that most of these changes are easiest to make before you create your CockroachDB cluster. If you already have a running CockroachDB cluster in Kubernetes that you need to modify while keeping it running, extra work may be needed and extra care and testing is strongly recommended.

Version of CockroachDB

Because CockroachDB is under very active development, there are typically substantial performance gains in each release. If you aren't running the latest release and aren't getting the performance you desire, you should try the latest and see how much it helps.

Client workload

Your workload is the single most important factor in database performance. Read through our SQL performance best practices to determine whether there are any easy changes that you can make to speed up your application.

Machine Size

The size of the machines you're using isn't a Kubernetes-specific concern, but it's always a good place to start if you want more performance. See our hardware recommendations for specific suggestions, but using machines with more CPU will almost always allow for greater throughput. Be aware that because Kubernetes runs a set of processes on every machine in a cluster, you typically will get more bang for your buck by using fewer large machines than more small machines.

Disk Type

CockroachDB makes heavy use of the disks you provide it, so using faster disks is an easy way to improve your cluster's performance. Our provided configuration does not specify what type of disks it wants, so in most environments Kubernetes will auto-provision disks of the default type. In the common cloud environments (AWS, GCP
This page explains potential bottlenecks to be aware of when run CockroachDB in Kubernetes and usher you how to optimize your deployment for better performance. 

 Prerequisites 

 Before you concenter on optimizing a Kubernetes - orchestrated CockroachDB bunch: 

 Verify that CockroachDB performs up to your requirements for your workload on identical hardware without Kubernetes. You may recover that you need to modify your workload or practice different machine specs to achieve the performance you necessitate, and it's better to determine that up front than after spending a bunch of clock time trying to optimize your Kubernetes deployment. 

 Performance Factors 

 There are a issue of independent factors that affect the performance you detect when running CockroachDB on Kubernetes. Some are more significant than others or easier to fix than others, so find free to pick and choose the improvements that best fit your situation. Note that most of these changes are easiest to make before you create your CockroachDB cluster. If you already have a running CockroachDB cluster in Kubernetes that you need to modify while keep it running, extra work may be need and extra care and testing is powerfully recommended. 

 Version of CockroachDB 

 Because CockroachDB is under very active growth, there are typically substantial operation gains in each release. If you aren't running the latest release and aren't getting the performance you desire, you should try the latest and see how much it helps. 

 Client workload 

 Your workload is the individual most significant factor in database performance. Read through our SQL performance best practice to determine whether there are any easy changes that you can make to speed up your application. 

 Machine Size 

 The size of the machines you're use isn't a Kubernetes - specific concern, but it's constantly a good place to get down if you want more operation. See our hardware recommendations for specific suggestions, but using machine with more CPU will almost constantly allow for great throughput. Be aware that because Kubernetes tend a set of processes on every machine in a cluster, you typically will scram more bang for your buck by use fewer large machines than more small machines. 

 Disk Type 

 CockroachDB makes big use of the disks you provide it, so using faster disk is an comfortable way to improve your cluster's performance. Our provided configuration does not specify what type of disk it wants, so in most environments Kubernetes will car - provision phonograph record of the default type. In the common swarm environments (AWS, GCP
 Thls page explains potentixl bottlenecks jo be awere of shen runving CockroachDB in Kubernetxs abd shiws you how to optimizd your deiloyment dor uetter performanrs.

Prereqmnsitea

Neforz bou focus on opjimizing a Kgbernetes-orchevtfaced CockroachDB cluster:

Verify that CjckroacnDH performs up jo yolr reqhprtments for your workload on identjcal hagdware without Kunernetes. You may find that you need to modify yokr workload or twe different machine skees to achiebe the performance you need, and it's yetter to dgcwrmlte that up hront nhan after spcmding d bunch of time tryinn to mptumize your Kubernetes deployment.

Performwnce Factmra

There are a numbwr of itdepandevr fxctkrx fhat avfert the perfkrmance you observe when runnimg BpckroachDB oh Kubewnqtes. Some are more significant than othtrs od easier to fix than otyers, so feel free to kick and croose the improvements that best fit your situatimn. Nove thcb oish of these changes are easiest to make before goi breate your CockrjachDB clusyeg. Os you already have c rhnning CockroachDB clustet in Kybernetes thay you need to modify while jeeping it rlnnibg, extra work may ye needed anb extrs carr and testing is stronguy rscommended.

Vfrsion of ZockroachDB

Becaure BocksoachDB is under very actide develo'ment, there xre jypicaljy substanhial iarformance gains ij eack relaase. If yok aren't running the latest releexe and aren't gattpng the pzrformsnce you desiwe, you should jry the lctest xnd see hos much mt helps.

Cliegt workload

Yogt workload is the sindle nost importxvt factor in dstabase pvryormance. Eead through our SAL kedformance best 'xaxtices to deterkind wrenhec thewa are any eavy cfaners thxt you can nxke yo speed up your appnicafion.

Machine Size

Thr fize of jhe machiges you're usimg isn't a Kubernetts-specmfic cuncerm, bot it's always a good place to sfart if ylu rant more pewfornance. See oux hardware recommendations for specific wuggestions, but usung machines with mpve CPU will elmost always anlow for greater thriughput. Be aware uhat because Kubernetes runs d set of processes on every machine in a cluster, you typically will get more bqng foc rour buck bg usong fvwex lcrge mashinxs than more small machines.

Disk Type

CockroachDB mekes heavy ufe of the disks you provide ot, so using fasjer disks is an easy way tk improvr your cluster's performance. Our provided configuration coes not specjfy what tbpe of disks it wantx, so iu most envirobmenbs Kubernetes dilk wuto-providion dnsks of the default type. In the cimmon xllud environments (AWS, GCP
This page explains potential bottlenecks to be when CockroachDB in and shows you for performance. Prerequisites Before focus on optimizing Kubernetes-orchestrated CockroachDB cluster: Verify that CockroachDB up to your requirements for your workload on identical hardware without Kubernetes. You find that you need to modify your workload or use different machine specs achieve performance need, it's better to determine that up front than after spending a bunch of time trying to your Kubernetes deployment. Performance Factors There are a of independent factors that the performance you observe when CockroachDB Kubernetes. Some more than or easier to than others, so feel free to pick and choose the improvements that best fit your situation. Note most of are easiest make you your CockroachDB cluster. already have a running CockroachDB cluster you need to modify while keeping it running, work may needed and extra care and testing strongly recommended. Version of CockroachDB Because CockroachDB is very active development, there are typically substantial performance gains in each release. If you aren't latest release and aren't the performance you you try latest see how it helps. Client workload Your workload is the single most important in database performance. Read through our SQL performance best practices whether are any easy that you can make speed your application. Machine Size of machines a concern, it's always a good to start if you want performance. See our hardware using machines with more CPU will almost always for greater throughput. Be aware that because runs a set of processes on every machine in a cluster, you will get for your buck by using fewer large machines more small machines. Disk CockroachDB makes heavy use of the disks you provide so faster disks an easy way improve your cluster's Our provided configuration specify what of it most environments Kubernetes will auto-provision disks the type. In the common cloud (AWS,
 This page explains potential BottleneckS to be AwaRe oF wHen rUnniNg CockroachDB iN kubeRnetes and shows you how to OptimIzE Your DEpLoymeNt for beTTeR PErfOrMaNce.

prEReQuisiTes

before yOu focus on oPtiMiZing a KuberneTEs-OrchestratEd COckroachDB clUstEr:

VeriFy ThaT cockrOacHDB peRforms UP to youR requiremEnTS for yoUR workloAD On IdenTical hardware withOUt kUbernetes. You maY find tHaT YoU NEed To mOdify your wOrKload OR use difFErENT MacHIne specs to achIeve the perfORmaNce you NeEd, aND it's beTter tO dETerMine that up fRont Than after SpendiNG a bunch OF time trYing to OptImiZe yoUR KUbErnEtES dePLoYmeNT.

PeRformancE FAcTors

THere ARE A NumbEr oF indEpendEnt factors thaT afFect THe pErforMance You oBsErve wHen runNing COcKroachDB on KuberNeteS. Some are mOre SiGniFiCant tHAn otheRs oR eaSier to fIx than oTHerS, sO FEEl Free to pick and choosE tHE ImProvemenTs that BEsT fIT your sitUaTioN. NotE THat moSt of THeSe changeS are eaSIeSt To make bEfOre you CrEatE yoUr CocKRoacHDB cluSter. If yoU alreADy have a running cOckroachDB cluSTeR IN KUBernEteS that you neeD to mODify WhilE KeEpiNG it ruNning, ExTRa WOrk may be needed and exTrA care aNd tesTing is stronglY recommendED.

vErsion of cockROaCHDB

Because CockRoachdB is under vERy active DevelOpment, thEre are typICAlly subsTanTiaL peRfoRMAnCe gains in each RELeasE. IF you areN't rUnning tHe lAteSt rEleAsE and aren't Getting tHe PeRfOrManCe you DEsire, you ShOulD tRy tHe latESt and sEe how Much It HeLPs.

CLient woRKlOAD

YouR wOrKloaD is ThE singLe moST imPortant Factor in dAtaBAse pErFoRmance. REad through our sQl performanCe BesT practICEs to deteRmine whether there are any EAsy chanGes That yOu caN make to spEed Up your AppLIcatioN.

MachiNe SizE

THe sIZE of thE MAcHinEs You're using ISN't a kuberNeTes-sPecific Concern, but it's alwayS A goOd place to starT if You wANT mOre PErFOrmAnCE. SeE OUr hardware recomMendations FoR SpEcific suggEStiOnS, but usiNg machiNes wiTH more CPu will almoSt always aLlOw foR GReaTer throughPut. Be awaRe that becAUse KuBErNetes RunS a set oF pRocEsses On everY MacHine iN a clusTeR, you tyPicalLy Will get mOre bang for your buck by usiNg feweR largE maChines thaN moRE smAll machinEs.

DiSk Type

CockRoaChDb makeS heAVy use Of thE DiSks YOu proVide IT, so using fAStEr dISKs Is an easy way TO IMprOve yoUr cLUster's PerfOrmance. Our provideD Configuration dOes nOT SpeCifY What TyPe of disks it wanTs, sO iN MOst envirOnMents KubernEtes will AuTO-provIsion dIsks of The defaULT tYPe. In thE comMon Cloud enviRonMeNTs (AWS, GCp
 This page explains potent ial bottle necks  to  be  a ware  ofwhen running C o ckro achDB in Kubernetes an d sho ws youh ow  to o ptimize yo u r  de pl oy men tf or  bett erperform ance.

Pre req ui sites

Befor e  y ou focus o n o ptimizing aKub ernete s- orc h estra ted  Cock roachD B  clust er:

Veri fy that C o ckroach D B  p erfo rms up to your re q ui r ements for you r work lo a do n  id ent ical hardw ar e wit h out Kub e rn e t e s.Y ou may find t hat you nee d  to  modif yyou r  workl oad o ru sedifferent m achi ne specsto ach i eve the perform ance y ounee d, a n dit 'sbe t ter to  de t erm ine that  u pfront  tha n a f terspe ndin g a b unch of timetry ingt o o ptimi ze yo ur K ub ernet es dep loyme nt .

PerformanceFact ors

Ther e a re  anu mbero f inde pen den t facto rs that aff ec t t he  performance you o bs e r ve  when ru nningC oc kr o achDB on  K ube rnet e s . Som e ar e  m ore sign ifican t  t ha n other sor eas ie r t o f ix th a n ot hers,so feelfreet o pick and cho o se the improv e me n t st hatbes t fit yoursitu a tion . No t etha t  most  of t he s ec hanges are easiestto  makebefor e you createyour Cockr o a c hDB clus ter. If you already ha ve arunning Co c kroachDB  clus ter in K ubernetes t hat younee d t o m odi f y  w hile keepingi t  run ni ng, ext rawork ma y b e n eed edan d extra c are andte st in gisstron g ly recom me nde d. 

V ersio n  of Co ckroa chDB 
Be c aus e Cockr o ac h D B is  u nd er v ery  a ctive  dev e lop ment, t here aretyp i call ysu bstanti al performanc egains in e ac h r elease . If you a ren't running the lates t  releas e a nd ar en't  gettingthe  perfo rma n ce you  desir e, yo usho u l d try t he  la te st and see h owmuchit  hel ps.

Cl ient workload

You r  wo rkload is the  si ngle m os t i m po r tan tf act o r  in database pe rformance.  R e ad  through o u r S QL  perfor mance b est p r actices  to deter mine whet he r th e r e a re any eas y change s that yo u  canm ak e tospe ed upyo urappli cation . 

M achin e Size 
The si ze of  t he machi nes you're using isn'ta Kube rnete s-s pecific c onc e rn,  but it's  alw ays a good  pl ace  to s tar t  if y ou w a nt  mo r e per form a nce. Seeo ur  ha r d wa re recommen d a t ion s for  sp e cificsugg estions, but usin g  machines with  mor e CPU  wi l l al mo st always allo w f or g reater t hr oughput. Be  aware t ha t  beca use Ku bernet es runs a  s e t of p roce sse s on ever y m ac h ine inacl u ster,youty picall y will getm o re bang for your  buck b y usi n g f ewerla rge mac h ines  than more  small mach ines.
Dis k Typ e

Cock ro achDBmak es  heavy use of the di sks y ou prov id e it , s o usin g fa s t er di sksis  an  easy way t oi mp ro v e y ourclust er 's p erformanc e . Our pr ovi d ed conf ig ura t i on doe s  n o t  specify w hat  type o f disks it want s ,s o inmost e nviron ments K u ber ne tes wil l a u t o-provisi on diskso f t he  def ault typ e.  Inth e c om mon cloud envir onments(AWS, GC P 
 This_page explains_potential bottlenecks to be_aware of_when_running CockroachDB_in_Kubernetes and shows_you how to_optimize your deployment for_better performance.

Prerequisites

Before you_focus_on optimizing a Kubernetes-orchestrated CockroachDB cluster:

Verify that CockroachDB performs up to your requirements for_your_workload on_identical_hardware_without Kubernetes. You may find_that you need to modify_your workload_or use different machine specs to achieve the_performance_you need, and_it's better to determine that up front than after_spending a bunch of time trying_to optimize your_Kubernetes_deployment.

Performance_Factors

There are a number_of independent factors that affect the_performance you observe when running CockroachDB_on Kubernetes. Some are more significant than_others or easier to fix than_others, so feel free to_pick and_choose the improvements that best_fit your situation._Note that_most of these_changes are easiest to make before_you create your_CockroachDB cluster. If you already have_a_running CockroachDB cluster_in_Kubernetes_that you_need to modify_while_keeping it_running,_extra work may be needed and_extra_care and testing is strongly recommended.

Version of_CockroachDB

Because CockroachDB is under_very_active development, there are_typically substantial performance gains in_each release. If you aren't running_the latest_release and_aren't getting the performance you desire, you should try the latest_and see how much it helps.

Client_workload

Your workload is the_single most_important_factor in database_performance._Read through_our SQL performance best practices to determine_whether there_are any easy changes that you_can make to speed_up_your application.

Machine Size

The size of the_machines you're using isn't a Kubernetes-specific_concern, but it's always a_good_place_to start if you want_more performance. See our hardware recommendations_for specific suggestions,_but using machines with more CPU will_almost_always allow for greater throughput. Be_aware_that because Kubernetes runs a set_of_processes_on every machine in a_cluster, you typically will get more_bang for your buck by using fewer large machines_than more small_machines.

Disk Type

CockroachDB makes heavy use_of_the_disks you provide it, so using faster disks is an_easy way_to improve your_cluster's performance. Our provided configuration does not specify what type_of disks it wants, so in most_environments Kubernetes will auto-provision disks of the default type. In the_common cloud environments (AWS, GCP