funksioni tabelar input<\/a><\/noindex>.<\/p>\n<\/p>\n
<\/p>\n
Nj\u00eb tjet\u00ebr antipattern \u2013 \u00ebsht\u00eb mikroshardimi. P\u00ebr shembull, ju duhet t\u00eb shardoni t\u00eb dh\u00ebnat dhe keni 5 server\u00eb, kurse nes\u00ebr do t\u00eb keni 6 server\u00eb. Dhe ju mendoni, si ta rishp\u00ebrndani k\u00ebto t\u00eb dh\u00ebna. Dhe n\u00eb vend t\u00eb k\u00ebsaj, ju i ndani jo n\u00eb 5 sharda, por n\u00eb 1,000 sharda. Dhe m\u00eb pas ju tregoni \u00e7do nj\u00eb nga k\u00ebto mikrosharda n\u00eb nj\u00eb server t\u00eb ve\u00e7ant\u00eb. Dhe ju do t\u00eb p\u00ebrfundoni, p\u00ebr shembull, me 200 ClickHouse n\u00eb nj\u00eb server, p\u00ebr shembull. Instance t\u00eb ve\u00e7anta n\u00eb porte t\u00eb ve\u00e7anta ose baza t\u00eb ve\u00e7anta t\u00eb t\u00eb dh\u00ebnave. <\/p>\n
<\/p>\n
<\/p>\n
Por n\u00eb ClickHouse kjo nuk \u00ebsht\u00eb shum\u00eb mir\u00eb. Sepse edhe nj\u00eb instance ClickHouse p\u00ebrpiqet t\u00eb p\u00ebrdor\u00eb t\u00eb gjitha burimet e disponueshme t\u00eb serverit p\u00ebr t\u00eb trajtuar nj\u00eb k\u00ebrkes\u00eb t\u00eb vetme. Q\u00eb \u00ebsht\u00eb, keni nj\u00eb server ndonj\u00ebher\u00eb dhe atje, p\u00ebr shembull, 56 b\u00ebrtham\u00eb procesori. Ju e ekzekutoni nj\u00eb k\u00ebrkes\u00eb q\u00eb zgjat nj\u00eb sekond\u00eb, dhe ajo do t\u00eb p\u00ebrdor\u00eb 56 b\u00ebrthama. Por n\u00ebse keni vendosur 200 ClickHouse n\u00eb nj\u00eb server, at\u00ebher\u00eb ndodhet q\u00eb do t\u00eb startojn\u00eb 10,000 thread-e. N\u00eb p\u00ebrgjith\u00ebsi, gjith\u00e7ka do t\u00eb shkoj\u00eb shum\u00eb keq.<\/p>\n
<\/p>\n
Arsyet e tjera jan\u00eb se shp\u00ebrndarja e pun\u00ebs midis k\u00ebtyre instanceve do t\u00eb jet\u00eb e pat\u00ebbarabart\u00eb. Disa p\u00ebrfundojn\u00eb m\u00eb her\u00ebt, disa m\u00eb von\u00eb. N\u00ebse gjith\u00eb kjo do t\u00eb ndodhte n\u00eb nj\u00eb instance, ClickHouse do ta merrte vet\u00eb p\u00ebrsip\u00ebr si t\u00eb shp\u00ebrndante t\u00eb dh\u00ebnat n\u00eb m\u00ebnyr\u00eb t\u00eb sakt\u00eb n\u00ebp\u00ebr thread-e. <\/p>\n
<\/p>\n
Dhe nj\u00eb arsye tjet\u00ebr \u00ebsht\u00eb se do t\u00eb keni nd\u00ebrveprim nd\u00ebrprocesor p\u00ebrmes TCP. T\u00eb dh\u00ebnat do t\u00eb duhet t\u00eb serializohen, deserializohen dhe kjo \u00ebsht\u00eb nj\u00eb sasi e madhe mikroshardesh. Do t\u00eb funksionoj\u00eb thjesht n\u00eb m\u00ebnyr\u00eb joefikase.<\/p>\n
<\/p>\n
<\/p>\n
Nj\u00eb tjet\u00ebr antipattern, ndon\u00ebse \u00ebsht\u00eb e v\u00ebshtir\u00eb ta quash t\u00eb till\u00eb. Kjo \u00ebsht\u00eb nj\u00eb sasi e madhe paragrege.<\/p>\n
<\/p>\n
N\u00eb p\u00ebrgjith\u00ebsi, paragrege \u2013 \u00ebsht\u00eb mir\u00eb. Keni pasur nj\u00eb miliard rreshta, e keni agreguar dhe tani keni 1,000 rreshta, dhe tani k\u00ebrkesa ekzekutohet menj\u00ebher\u00eb. Gjith\u00e7ka \u00ebsht\u00eb e shk\u00eblqyer. K\u00ebshtu mund t\u00eb b\u00ebni. Dhe p\u00ebr k\u00ebt\u00eb, madje edhe n\u00eb ClickHouse ka nj\u00eb tip t\u00eb ve\u00e7ant\u00eb tabele AggregatingMergeTree, e cila b\u00ebn agregimin inkremental nd\u00ebrsa ose b\u00ebni inserte t\u00eb dh\u00ebnash. <\/p>\n
<\/p>\n
Por ndodhin raste kur ju mendoni se do t\u00eb agregojm\u00eb t\u00eb dh\u00ebnat k\u00ebshtu dhe p\u00ebrs\u00ebri do t\u00eb agregojm\u00eb t\u00eb dh\u00ebnat. Dhe n\u00eb nj\u00eb departament fqinj, nuk kam d\u00ebshir\u00eb t\u00eb flas se cili, p\u00ebrdorin tabela SummingMergeTree p\u00ebr t\u00eb b\u00ebr\u00eb p\u00ebrllogaritje sipas \u00e7el\u00ebsit primar, dhe si \u00e7el\u00ebs primar p\u00ebrdorin rreth 20 kolona t\u00eb ndryshme. Un\u00eb p\u00ebr hir t\u00eb konspiracionit kam ndryshuar emrat e disa kolonave, por p\u00ebrllogarisni se k\u00ebshtu \u00ebsht\u00eb.<\/p>\n
<\/p>\n
<\/p>\n
Dhe \u00e7far\u00eb probleme shfaqen? S\u00eb pari, volumi i t\u00eb dh\u00ebnave nuk zvog\u00eblohet shum\u00eb. P\u00ebr shembull, zvog\u00eblohet n\u00eb tre her\u00eb. Tre her\u00eb \u2013 do t\u00eb ishte nj\u00eb \u00e7mim i mir\u00eb p\u00ebr t\u00eb lejuar mund\u00ebsi t\u00eb pakufizuara p\u00ebr analiza q\u00eb shfaqen, n\u00ebse t\u00eb dh\u00ebnat tuaja nuk jan\u00eb agreguar. N\u00ebse t\u00eb dh\u00ebnat jan\u00eb t\u00eb agreguara, at\u00ebher\u00eb n\u00eb vend t\u00eb analizave, do t\u00eb merrni vet\u00ebm statistika t\u00eb mjerueshme. <\/p>\n
<\/p>\n
Dhe \u00e7far\u00eb ve\u00e7an\u00ebrisht nervon? Ato q\u00eb njer\u00ebzit nga departamenti fqinj vijn\u00eb dhe k\u00ebrkojn\u00eb ndonj\u00ebher\u00eb t\u00eb shtojn\u00eb nj\u00eb kolon\u00eb tjet\u00ebr n\u00eb \u00e7el\u00ebsin primar. Pra, ne kemi agreguar t\u00eb dh\u00ebnat k\u00ebshtu, por tani duam pak m\u00eb shum\u00eb. Por n\u00eb ClickHouse nuk ka ndryshim t\u00eb \u00e7el\u00ebsit primar. Pra, duhet t\u00eb shkruajm\u00eb disa skripte n\u00eb C++. Dhe un\u00eb nuk i p\u00eblqej skriptet, p\u00ebr shkak se jan\u00eb n\u00eb C++ ose jo.<\/p>\n
<\/p>\n
Dhe n\u00ebse shikoni p\u00ebr \u00e7far\u00eb \u00ebsht\u00eb krijuar ClickHouse, t\u00eb dh\u00ebnat e paagreguara jan\u00eb pik\u00ebrisht skenari p\u00ebr t\u00eb cilin \u00ebsht\u00eb krijuar. N\u00ebse e p\u00ebrdorni ClickHouse p\u00ebr t\u00eb dh\u00ebnat e paagreguara, at\u00ebher\u00eb po b\u00ebni gjith\u00e7ka si\u00e7 duhet. N\u00ebse po agregoni, at\u00ebher\u00eb ndonj\u00ebher\u00eb mund t\u00eb falet. <\/p>\n
<\/p>\n
<\/p>\n
Nj\u00eb rast tjet\u00ebr interesant \u00ebsht\u00eb ky i k\u00ebrkesave n\u00eb nj\u00eb cik\u00ebl t\u00eb pafund. Her\u00eb pas here hyj n\u00eb nj\u00eb server prodhimi dhe shoh p\u00ebr proceset. Dhe \u00e7do her\u00eb zbuloj se ndodhin gj\u00ebra t\u00eb tmerrshme. <\/p>\n
<\/p>\n
P\u00ebr shembull, k\u00ebto. K\u00ebtu menj\u00ebher\u00eb \u00ebsht\u00eb e qart\u00eb se mund t\u00eb ishte b\u00ebr\u00eb gjith\u00e7ka n\u00eb nj\u00eb k\u00ebrkes\u00eb. Thjesht shkruani atje url in dhe list\u00ebn.<\/p>\n
<\/p>\n
<\/p>\n
Pse shum\u00eb nga k\u00ebto k\u00ebrkesa n\u00eb nj\u00eb cik\u00ebl t\u00eb pafund jan\u00eb t\u00eb k\u00ebqija? N\u00ebse indeksi nuk p\u00ebrdoret, do t\u00eb keni shum\u00eb kalime p\u00ebr t\u00eb nj\u00ebjtat t\u00eb dh\u00ebna. Por n\u00ebse indeksi p\u00ebrdoret, p\u00ebr shembull, keni nj\u00eb \u00e7el\u00ebs primar sipas ru dhe shkruani url = di\u00e7ka. Dhe mendoni se do t\u00eb lexohet sakt\u00ebsisht nga tabela nj\u00eb url, do t\u00eb jet\u00eb gjith\u00e7ka n\u00eb rregull. Por n\u00eb t\u00eb v\u00ebrtet\u00eb nuk \u00ebsht\u00eb. Sepse ClickHouse b\u00ebn gjith\u00e7ka n\u00eb grupe. <\/p>\n
<\/p>\n
Kur ai duhet t\u00eb lexoj\u00eb nj\u00eb gam\u00eb t\u00eb caktuar t\u00eb t\u00eb dh\u00ebnave, lexon pak m\u00eb shum\u00eb, sepse indeksi n\u00eb ClickHouse \u00ebsht\u00eb i rrall\u00eb. Ky indeks nuk lejon t\u00eb gjesh nj\u00eb rresht t\u00eb ve\u00e7ant\u00eb n\u00eb tabel\u00eb, vet\u00ebm nj\u00eb gam\u00eb t\u00eb caktuar. T\u00eb dh\u00ebnat kompresohen n\u00eb blloqe. P\u00ebr t\u00eb lexuar nj\u00eb rresht, duhet t\u00eb marr\u00ebsh t\u00ebr\u00eb nj\u00eb bllok dhe ta dekompresosh. Dhe n\u00ebse b\u00ebn shum\u00eb k\u00ebrkesa, do t\u00eb kesh shum\u00eb p\u00ebrputhje t\u00eb tilla, dhe shum\u00eb pun\u00eb do t\u00eb kryhet p\u00ebrs\u00ebri e p\u00ebrs\u00ebri.<\/p>\n
<\/p>\n
<\/p>\n
Dhe si nj\u00eb bonus mund t\u00eb v\u00ebreni se n\u00eb ClickHouse nuk duhet t\u00eb keni frik\u00eb t\u00eb d\u00ebrgoni madje megabajt dhe madje qindra megabajt n\u00eb seksionin IN. E mbaj mend nga praktika jon\u00eb, se n\u00ebse n\u00eb MySQL d\u00ebrgojm\u00eb shum\u00eb vlera n\u00eb seksionin IN, p\u00ebr shembull, d\u00ebrgojm\u00eb aty 100 megabajt t\u00eb disa numrave, MySQL konsumon 10 gigabajt memorie dhe m\u00eb shum\u00eb nuk ndodh asgj\u00eb, gjith\u00e7ka funksionon keq. <\/p>\n
<\/p>\n
Dhe e dyta \u2013 \u00ebsht\u00eb se n\u00eb ClickHouse, n\u00ebse k\u00ebrkesat tuaja p\u00ebrdorin indeksin, at\u00ebher\u00eb kjo \u00ebsht\u00eb gjithmon\u00eb jo m\u00eb ngadal\u00eb se skenimi i plot\u00eb, dometh\u00ebn\u00eb, n\u00ebse duhet t\u00eb lexosh pothuajse t\u00eb gjith\u00eb tabel\u00ebn, do t\u00eb shkoj\u00eb radhazi dhe do t\u00eb lexoj\u00eb t\u00eb gjith\u00eb tabel\u00ebn. N\u00eb p\u00ebrgjith\u00ebsi, ai do t\u00eb merret me t\u00eb vet\u00eb.<\/p>\n
<\/p>\n
Por megjithat\u00eb ka disa v\u00ebshtir\u00ebsi. P\u00ebr shembull, q\u00eb IN me n\u00ebnk\u00ebrkes\u00eb nuk p\u00ebrdor indeksin. Por kjo \u00ebsht\u00eb problemi yn\u00eb dhe duhet ta rregullojm\u00eb. Nuk ka asgj\u00eb themelore k\u00ebtu. Do ta rregullojm\u00eb. <\/p>\n
<\/p>\n
Dhe nj\u00eb gj\u00eb tjet\u00ebr interesante \u2013 \u00ebsht\u00eb se n\u00ebse keni nj\u00eb k\u00ebrkes\u00eb shum\u00eb t\u00eb gjat\u00eb dhe p\u00ebrpunimi i k\u00ebrkesave \u00ebsht\u00eb i shp\u00ebrndar\u00eb, at\u00ebher\u00eb kjo k\u00ebrkes\u00eb shum\u00eb e gjat\u00eb do t\u00eb d\u00ebrgohet n\u00eb \u00e7do server pa kompresim. P\u00ebr shembull, 100 megabajt dhe 500 server\u00eb. Dhe, p\u00ebr pasoj\u00eb, do t\u00eb transmetohen 50 gigabajt p\u00ebr rrjet. Do t\u00eb d\u00ebrgohet dhe pastaj gjith\u00e7ka do t\u00eb ekzekutohet me sukses.<\/p>\n
<\/p>\n
* tashm\u00eb e p\u00ebrdor; gjith\u00e7ka e riparuar, si\u00e7 ishte premtuar.<\/p>\n
<\/p>\n
<\/p>\n
Dhe nj\u00eb rast mjaft i zakonsh\u00ebm \u00ebsht\u00eb n\u00ebse k\u00ebrkesat vijn\u00eb nga API. P\u00ebr shembull, ju keni krijuar nj\u00eb sh\u00ebrbim tuajin. Dhe n\u00ebse sh\u00ebrbimi juaj \u00ebsht\u00eb i nevojsh\u00ebm p\u00ebr dik\u00eb, at\u00ebher\u00eb keni hapur API dhe tashm\u00eb brenda dy dit\u00ebsh shihni se po ndodh di\u00e7ka e paqart\u00eb. T\u00eb gjitha jan\u00eb t\u00eb mbingarkuara dhe disa k\u00ebrkesa t\u00eb tmerrshme po vijn\u00eb, t\u00eb cilat kurr\u00eb nuk duhet t\u00eb ishin. <\/p>\n
<\/p>\n
Dhe zgjidhja \u00ebsht\u00eb nj\u00eb. N\u00ebse keni hapur API, at\u00ebher\u00eb do t'ju duhet ta kufizoni at\u00eb. P\u00ebr shembull, t\u00eb vendosni kuota t\u00eb ndryshme. Nuk ka mund\u00ebsi t\u00eb tjera normale. N\u00ebse jo, menj\u00ebher\u00eb do t\u00eb shkruajn\u00eb nj\u00eb skript dhe do t\u00eb keni probleme. <\/p>\n
<\/p>\n
N\u00eb ClickHouse ka nj\u00eb mund\u00ebsi t\u00eb ve\u00e7ant\u00eb \u2013 \u00ebsht\u00eb num\u00ebrimi i kuotave. Madje, mund t\u00eb kaloni \u00e7el\u00ebsin tuaj t\u00eb kuotave. Kjo, p\u00ebr shembull, \u00ebsht\u00eb identifikuesi i brendsh\u00ebm i p\u00ebrdoruesit. Dhe kuotat do t\u00eb llogariten n\u00eb m\u00ebnyr\u00eb t\u00eb pavarur p\u00ebr secilin prej tyre. <\/p>\n
<\/p>\n
<\/p>\n
Tani ka nj\u00eb gj\u00eb tjet\u00ebr interesante. Kjo \u00ebsht\u00eb replikimi me manual. <\/p>\n
<\/p>\n
Di shum\u00eb raste kur, pavar\u00ebsisht se ClickHouse ka mb\u00ebshtetje t\u00eb integruar p\u00ebr replikimin, njer\u00ebzit replikojn\u00eb ClickHouse manualisht.<\/p>\n
<\/p>\n
Cili \u00ebsht\u00eb parimi? Keni nj\u00eb pipeline p\u00ebr procesimin e t\u00eb dh\u00ebnave. Dhe ai punon n\u00eb m\u00ebnyr\u00eb t\u00eb pavarur, p\u00ebr shembull, n\u00eb qendrat e t\u00eb dh\u00ebnave t\u00eb ndryshme. Regjistroni t\u00eb dh\u00ebna t\u00eb nj\u00ebjta n\u00eb ClickHouse n\u00eb m\u00ebnyr\u00eb t\u00eb nj\u00ebjt\u00eb. Sidoqoft\u00eb, praktika tregon se t\u00eb dh\u00ebnat ende do t\u00eb shp\u00ebrndahen p\u00ebr shkak t\u00eb disa ve\u00e7orive n\u00eb kodin tuaj. Shpresoj q\u00eb jo n\u00eb kodin tuaj. <\/p>\n
<\/p>\n
Dhe periodikisht do t\u00eb duhet ta sinkronizoni manualisht. P\u00ebr shembull, nj\u00eb her\u00eb n\u00eb muaj administratoret b\u00ebjn\u00eb rsync.<\/p>\n
<\/p>\n
N\u00eb t\u00eb v\u00ebrtet\u00eb, \u00ebsht\u00eb shum\u00eb m\u00eb e thjesht\u00eb t\u00eb p\u00ebrdorni replikimin e integruar n\u00eb ClickHouse. Por k\u00ebtu mund t\u00eb ket\u00eb disa kund\u00ebrshtime, sepse p\u00ebr k\u00ebt\u00eb duhet t\u00eb p\u00ebrdorni ZooKeeper. Nuk do t\u00eb flas ndonj\u00eb gj\u00eb t\u00eb keqe p\u00ebr ZooKeeper, n\u00eb parim, sistemi funksionon, por ka raste kur njer\u00ebzit nuk e p\u00ebrdorin p\u00ebr shkak t\u00eb frik\u00ebs nga Java, sepse ClickHouse \u00ebsht\u00eb nj\u00eb sistem i shk\u00eblqyer i shkruar n\u00eb C++, t\u00eb cilin mund ta p\u00ebrdorni dhe gjith\u00e7ka do t\u00eb shkoj\u00eb mrekullisht. Nd\u00ebrsa ZooKeeper \u00ebsht\u00eb n\u00eb Java. Dhe ndonj\u00ebher\u00eb nuk d\u00ebshiron ta shikosh, por mund t\u00eb p\u00ebrdor\u00ebsh replikimin me manual. <\/p>\n
<\/p>\n
<\/p>\n
ClickHouse \u00ebsht\u00eb nj\u00eb sistem praktik. Ai merr parasysh nevojat tuaja. N\u00ebse keni replikim manual, mund t\u00eb krijoni nj\u00eb tabel\u00eb t\u00eb Distribuar q\u00eb shikon replikat tuaja manuale dhe automatikisht b\u00ebn failover mes tyre. Dhe ka madje nj\u00eb opsion t\u00eb ve\u00e7ant\u00eb q\u00eb lejon shmangien e flukseve, edhe n\u00ebse replikat tuaja shp\u00ebrndahen sistematikisht.<\/p>\n
<\/p>\n
<\/p>\n
M\u00eb pas mund t\u00eb ket\u00eb probleme n\u00ebse p\u00ebrdorni mjete tabelash primitive. ClickHouse \u00ebsht\u00eb nj\u00eb nd\u00ebrtues i till\u00eb, n\u00eb t\u00eb cilin ka shum\u00eb engine tabelash t\u00eb ndryshme. P\u00ebr t\u00eb gjitha rastet serioze, si\u00e7 shkruhet n\u00eb dokumentacion, p\u00ebrdorni tabelat e familjes MergeTree. Nd\u00ebrsa t\u00eb gjitha t\u00eb tjerat \u2013 jan\u00eb k\u00ebshtu, p\u00ebr raste t\u00eb ve\u00e7anta ose p\u00ebr teste.<\/p>\n
<\/p>\n
N\u00eb tabel\u00ebn MergeTree nuk \u00ebsht\u00eb e nevojshme t\u00eb keni ndonj\u00eb dat\u00eb dhe or\u00eb. Mund ta p\u00ebrdorni gjithsesi. N\u00ebse nuk ka dat\u00eb dhe or\u00eb, shkruani se default \u00ebsht\u00eb viti 2000. Kjo do t\u00eb funksionoj\u00eb dhe nuk do t\u00eb k\u00ebrkoj\u00eb burime. <\/p>\n
<\/p>\n
N\u00eb versionin e ri t\u00eb serverit, ju mund t\u00eb specifikoni madje q\u00eb t\u00eb keni nj\u00eb ndarje t\u00eb personalizuar pa \u00e7el\u00ebsin e ndarjes. Kjo do t\u00eb jet\u00eb e nj\u00ebjt\u00eb. <\/p>\n
<\/p>\n
<\/p>\n
Nga ana tjet\u00ebr, mund t\u00eb p\u00ebrdorni engine t\u00eb thjesht\u00eb tabelash. P\u00ebr shembull, ngarkoni t\u00eb dh\u00ebnat nj\u00eb her\u00eb dhe shihni, provoni dhe fshini. Mund t\u00eb p\u00ebrdorni Log.<\/p>\n
<\/p>\n
Ose ruajtja e volumit t\u00eb vog\u00ebl p\u00ebr p\u00ebrpunim t\u00eb p\u00ebrkohsh\u00ebm \u2013 kjo \u00ebsht\u00eb StripeLog ose TinyLog.<\/p>\n
<\/p>\n
Memory mund t\u00eb p\u00ebrdoret, n\u00ebse volumi i t\u00eb dh\u00ebnave \u00ebsht\u00eb i vog\u00ebl dhe thjesht t\u00eb provoni di\u00e7ka n\u00eb RAM. <\/p>\n
<\/p>\n
<\/p>\n
ClickHouse nuk e p\u00eblqen shum\u00eb t\u00eb dh\u00ebnat e tepruar normalizuar. <\/p>\n
<\/p>\n
Ja nj\u00eb shembull tipik. Kjo \u00ebsht\u00eb nj\u00eb sasi e madhe URL-sh. I keni vendosur ato n\u00eb nj\u00eb tabel\u00eb fqinje. Dhe pastaj vendos\u00ebt t\u00eb b\u00ebni JOIN me to, por kjo nuk do t\u00eb funksionoj\u00eb n\u00eb p\u00ebrgjith\u00ebsi, sepse ClickHouse mb\u00ebshtet vet\u00ebm Hash JOIN. N\u00ebse nuk ka mjaft RAM p\u00ebr shum\u00eb t\u00eb dh\u00ebna q\u00eb duhet t\u00eb bashkohen, at\u00ebher\u00eb JOIN nuk do t\u00eb funksionoj\u00eb. <\/p>\n
<\/p>\n
N\u00ebse t\u00eb dh\u00ebnat kan\u00eb kardinalitet t\u00eb madh, at\u00ebher\u00eb mos u shqet\u00ebsoni, ruani ato n\u00eb nj\u00eb format denormalizuar, URL-t\u00eb direkt n\u00eb tabel\u00ebn kryesore. <\/p>\n
<\/p>\n
* tani n\u00eb ClickHouse ka edhe merge join dhe ai funksionon n\u00eb kushte kur t\u00eb dh\u00ebnat p\u00ebr intermediary nuk p\u00ebrputhen n\u00eb RAM. Por kjo nuk \u00ebsht\u00eb efikase dhe rekomandimi mbetet n\u00eb fuqi.<\/p>\n
<\/p>\n
<\/p>\n
Edhe disa shembuj t\u00eb tjer\u00eb, por tashm\u00eb dyshoj n\u00ebse ata jan\u00eb antipattern. <\/p>\n
<\/p>\n
N\u00eb ClickHouse ka nj\u00eb disavantazh t\u00eb njohur. Ai nuk mb\u00ebshtet azhurnime. N\u00eb nj\u00eb far\u00eb kuptimi, kjo \u00ebsht\u00eb edhe e mir\u00eb. N\u00ebse keni disa t\u00eb dh\u00ebna t\u00eb r\u00ebnd\u00ebsishme, p\u00ebr shembull, llogaritarin\u00eb, askush nuk do t\u00eb mund t'i d\u00ebrgoj\u00eb, sepse nuk ka azhurnime.<\/p>\n
<\/p>\n
* mb\u00ebshtetje p\u00ebr azhurnim dhe fshirje n\u00eb regjimin batch \u00ebsht\u00eb shtuar prej koh\u00ebsh.<\/p>\n
<\/p>\n
Por ka disa m\u00ebnyra speciale, q\u00eb lejojn\u00eb azhurnimet si\u00e7 do t\u00eb ishin n\u00eb sfond. P\u00ebr shembull, tabelat e tipit ReplaceMergeTree. Ato b\u00ebjn\u00eb azhurnime gjat\u00eb bashkimeve n\u00eb sfond. Mund ta forconi k\u00ebt\u00eb n\u00ebp\u00ebrmjet optimize table. Por mos e b\u00ebni k\u00ebt\u00eb shum\u00eb shpesh, sepse do t\u00eb p\u00ebrb\u00ebj\u00eb rip\u00ebrpunim t\u00eb plot\u00eb t\u00eb ndarjes. <\/p>\n
<\/p>\n
JOIN t\u00eb shp\u00ebrndara n\u00eb ClickHouse \u2013 gjithashtu nuk trajtohen mir\u00eb nga planifikuesi i k\u00ebrkesave. <\/p>\n
<\/p>\n
E keqe, por ndonj\u00ebher\u00eb \u00ebsht\u00eb n\u00eb rregull.<\/p>\n
<\/p>\n
P\u00ebrdorimi i ClickHouse vet\u00ebm p\u00ebr t\u00eb lexuar t\u00eb dh\u00ebnat p\u00ebrmes select.<\/p>\n
<\/p>\n
Nuk e doja t\u00eb rekomandoj t\u00eb p\u00ebrdor\u00ebsh ClickHouse p\u00ebr llogaritje t\u00eb m\u00ebdha. Por nuk \u00ebsht\u00eb pik\u00ebrisht k\u00ebshtu, sepse ne tashm\u00eb po largohemi nga kjo rekomandim. Dhe s\u00eb fundmi, kemi shtuar mund\u00ebsin\u00eb p\u00ebr t\u00eb aplikuar modele t\u00eb m\u00ebsimit t\u00eb makineris\u00eb n\u00eb ClickHouse \u2013 Catboost. Dhe kjo m\u00eb shqet\u00ebson, sepse mendoj: \"\u00c7far\u00eb tmerri. Sa shum\u00eb cikle p\u00ebr bajt del?!\". M\u00eb vjen shum\u00eb keq t\u2019i harxhoj ciklet p\u00ebr bajta. <\/p>\n
<\/p>\n
<\/p>\n
Por mos ki frik\u00eb, instaloj ClickHouse, gjith\u00e7ka do t\u00eb shkoj\u00eb mir\u00eb. N\u00ebse ndodh ndonj\u00eb gj\u00eb, kemi nj\u00eb komunitet. Me t\u00eb v\u00ebrtet\u00eb, komuniteti \u2013 jeni ju. Dhe n\u00ebse keni ndonj\u00eb problem, mund t\u00eb hyni n\u00eb bised\u00ebn ton\u00eb, dhe shpresoj q\u00eb do t'ju ndihmojn\u00eb. <\/p>\n
<\/p>\n
Pyetje<\/p>\n
<\/p>\n
Faleminderit p\u00ebr prezantimin! Ku mund t\u00eb ankohem p\u00ebr r\u00ebnien e ClickHouse?<\/em><\/p>\n<\/p>\n
Mund t\u00eb ankohesh personalisht tek un\u00eb n\u00eb k\u00ebt\u00eb moment. <\/p>\n
<\/p>\n
Sapo kam filluar t\u00eb p\u00ebrdor ClickHouse. Menj\u00ebher\u00eb e kam rr\u00ebzuar interfacin cli.<\/em><\/p>\n<\/p>\n
T\u00eb lumt\u00eb. <\/p>\n
<\/p>\n
Pak m\u00eb von\u00eb e kam rr\u00ebzuar serverin me nj\u00eb selektor t\u00eb vog\u00ebl.<\/em><\/p>\n<\/p>\n
Ke talent. <\/p>\n
<\/p>\n
Kam hapur nj\u00eb bug n\u00eb GitHub, por e kan\u00eb injoruar.<\/em> <\/p>\n<\/p>\n
T\u00eb shohim. <\/p>\n
<\/p>\n
Aleksej m\u00eb \u00e7oi me mashtrim n\u00eb prezantim, duke m\u00eb premtuar se do t\u00eb tregonte se si e comproni t\u00eb dh\u00ebnat brenda.<\/em><\/p>\n<\/p>\n
Shum\u00eb thjesht\u00eb. <\/p>\n
<\/p>\n
K\u00ebt\u00eb e kuptova q\u00eb dje. M\u00eb shum\u00eb konkret\u00ebsi.<\/em> <\/p>\n<\/p>\n
Nuk ka ndonj\u00eb hile t\u00eb tmerrshme. Thjesht \u00ebsht\u00eb kompresim me blloqe. N\u00eb m\u00ebnyr\u00eb default p\u00ebrdoret LZ4, mund t\u00eb aktivizosh ZSTD*. Blloqet jan\u00eb nga 64 kilobajt deri n\u00eb 1 megabajt.<\/p>\n
<\/p>\n
*ka gjithashtu mb\u00ebshtetje p\u00ebr kodek\u00ebt e specializuar t\u00eb kompresimit, t\u00eb cilat mund t\u00eb p\u00ebrdoren n\u00eb zinxhir me algoritme t\u00eb tjera.<\/p>\n
<\/p>\n
A jan\u00eb t\u00eb dh\u00ebnat n\u00eb blloqe thjesht t\u00eb pap\u00ebrpunuara?<\/em><\/p>\n<\/p>\n
Jo krejt\u00ebsisht t\u00eb pap\u00ebrpunuara. Ka lista. N\u00ebse ke nj\u00eb kolon\u00eb numerike, atje numrat jan\u00eb renditur radhazi n\u00eb nj\u00eb list\u00eb. <\/p>\n
<\/p>\n
Kuptohet.<\/em> <\/p>\n<\/p>\n
Aleksej, shembulli q\u00eb ishte me uniqExact mbi IP-t\u00eb, pra, ajo q\u00eb uniqExact llogaritet m\u00eb ngadal\u00eb mbi stringje sesa mbi numra dhe k\u00ebshtu me radh\u00eb. Dhe n\u00ebse ne p\u00ebrdorim nj\u00eb nd\u00ebrrim dhe do t\u00eb kthejm\u00eb n\u00eb momentin e leximit? Pra, ju duket se that\u00eb se n\u00eb disk nuk dallon shum\u00eb. N\u00ebse ne lexojm\u00eb stringje nga disku, kthejm\u00eb, a do t\u00eb kemi m\u00eb shpejt agregat\u00ebt apo jo? Apo ndoshta gjithsesi do t\u00eb fitojm\u00eb pak k\u00ebtu? M\u00eb duket se e keni testuar k\u00ebt\u00eb, por p\u00ebr ndonj\u00eb arsye nuk e keni p\u00ebrmendur n\u00eb benchmarking.<\/em> <\/p>\n<\/p>\n
Mendoj se do t\u00eb jet\u00eb m\u00eb i ngadalsh\u00ebm se sa pa kast. N\u00eb k\u00ebt\u00eb rast, duhet t\u00eb shp\u00ebrndajm\u00eb adres\u00ebn IP nga stringu. Sigurisht, n\u00eb ClickHouse, shp\u00ebrndarja e adresave IP \u00ebsht\u00eb optimizuar gjithashtu. Ne kemi punuar shum\u00eb p\u00ebr k\u00ebt\u00eb, por atje ju keni numrat t\u00eb shkruar n\u00eb form\u00ebn e dhjet\u00eb mij\u00ebshit. Shum\u00eb e pak\u00ebndshme. Nga ana tjet\u00ebr, funksioni uniqExact do t\u00eb punoj\u00eb m\u00eb ngadal\u00eb mbi stringje jo vet\u00ebm sepse jan\u00eb stringje, por gjithashtu p\u00ebr shkak se zgjidhet nj\u00eb specializim tjet\u00ebr i algoritmit. Stringjet thjesht p\u00ebrpunohen ndryshe.<\/p>\n
<\/p>\n
Dhe n\u00ebse marrim nj\u00eb tip m\u00eb primitiv t\u00eb t\u00eb dh\u00ebnave? P\u00ebr shembull, shkruam user id, q\u00eb kemi brenda, e shkruam si string, dhe pastaj e kastojm\u00eb, do t\u00eb jet\u00eb m\u00eb arg\u00ebtuese apo jo?<\/em><\/p>\n<\/p>\n
Kam dyshime. Mendoj se do t\u00eb jet\u00eb edhe m\u00eb trishtues, sepse t\u00eb shp\u00ebrndash numrat \u00ebsht\u00eb nj\u00eb problem serioz. M\u00eb duket se ky kolegu kishte madje nj\u00eb referat mbi tem\u00ebn se sa e v\u00ebshtir\u00eb \u00ebsht\u00eb t\u00eb shp\u00ebrndash numrat n\u00eb form\u00ebn e dhjet\u00eb mij\u00ebshit, ndoshta jo. <\/p>\n
<\/p>\n
Alexey, faleminderit shum\u00eb p\u00ebr referatin! Dhe gjithashtu faleminderit shum\u00eb p\u00ebr ClickHouse! Kam nj\u00eb pyetje n\u00eb lidhje me planet. A ka ndonj\u00eb plan p\u00ebr nj\u00eb karakteristik\u00eb q\u00eb lejon p\u00ebrdit\u00ebsimin e fjalor\u00ebve jo plot\u00ebsisht?<\/em><\/p>\n<\/p>\n
Pra, nj\u00eb ri-ngarkim t\u00eb pjessh\u00ebm?<\/p>\n
<\/p>\n
Po, po. Nj\u00eb mund\u00ebsi p\u00ebr t\u00eb caktuar aty nj\u00eb fush\u00eb MySQL, pra, p\u00ebr t\u00eb p\u00ebrdit\u00ebsuar pas, q\u00eb t\u00eb ngarkohet vet\u00ebm k\u00ebto t\u00eb dh\u00ebna, n\u00ebse fjalori \u00ebsht\u00eb shum\u00eb i madh.<\/em><\/p>\n<\/p>\n
Nj\u00eb karakteristik\u00eb shum\u00eb interesante. Dhe, m\u00eb duket, ndonj\u00eb njeri e kishte propozuar at\u00eb n\u00eb bised\u00ebn ton\u00eb. Ndoshta ishit ju. <\/p>\n
<\/p>\n
Nuk mendoj se isha un\u00eb.<\/em><\/p>\n<\/p>\n
Shk\u00eblqyesh\u00ebm, tani del se jan\u00eb dy k\u00ebrkesa. Dhe mund t\u00eb filloni ngadal\u00eb. Por menj\u00ebher\u00eb d\u00ebshiroj t'ju paralajm\u00ebroj se kjo karakteristik\u00eb \u00ebsht\u00eb mjaft e thjesht\u00eb p\u00ebr t'u zbatuar. Pra, n\u00eb ide, duhet thjesht t\u00eb shkruani numrin e versionit n\u00eb tabel\u00eb dhe pastaj t\u00eb shkruani: versioni \u00ebsht\u00eb m\u00eb i vog\u00ebl se kaq. Dhe kjo do t\u00eb thot\u00eb se, shum\u00eb p\u00ebr fat, ne do t'ua propozojm\u00eb k\u00ebt\u00eb entuziast\u00ebve. A jeni entuziast? <\/p>\n
<\/p>\n
Po, por fatkeq\u00ebsisht, jo n\u00eb C++.<\/em><\/p>\n<\/p>\n
A e din\u00eb koleg\u00ebt tuaj t\u00eb shkruajn\u00eb n\u00eb C++? <\/p>\n
<\/p>\n
Do t\u00eb gjej dik\u00eb.<\/em><\/p>\n<\/p>\n
Shk\u00eblqyesh\u00ebm*.<\/p>\n
<\/p>\n
* mund\u00ebsia u shtua dy muaj pas referatit \u2013 e zhvilloi autori i pyetjes dhe d\u00ebrgoi k\u00ebrkes\u00ebn e tij p\u00ebr t\u00ebrheqje pull request<\/a><\/noindex>.<\/p>\n<\/p>\n
Faleminderit!<\/em><\/p>\n<\/p>\n
P\u00ebrsh\u00ebndetje! Faleminderit p\u00ebr raportin! Ju p\u00ebrmend\u00ebt se ClickHouse konsumon shum\u00eb mir\u00eb t\u00eb gjitha burimet q\u00eb ka n\u00eb dispozicion. Dhe fol\u00ebsi pran\u00eb Luksoft p\u00ebrmendi zgjidhjen e tij p\u00ebr Post\u00ebn e Rusis\u00eb. Ai tha se u p\u00eblqeu shum\u00eb ClickHouse, por nuk e p\u00ebrdor\u00ebn at\u00eb kund\u00ebr konkurentit t\u00eb tyre kryesor pik\u00ebrisht sepse konsumonte gjith\u00eb procesorin. A ka ndonj\u00eb mund\u00ebsi p\u00ebr ta kufizuar ClickHouse-n q\u00eb t\u00eb mos konsumoj\u00eb gjith\u00e7ka q\u00eb i ofrohet?<\/em><\/p>\n<\/p>\n
Po, \u00ebsht\u00eb e mundur dhe shum\u00eb e leht\u00eb. N\u00ebse d\u00ebshironi q\u00eb t\u00eb konsumoni m\u00eb pak b\u00ebrthama, thjesht shkruani set max_threads = 1<\/code>. Dhe gjith\u00e7ka, do t\u00eb ekzekutoj\u00eb k\u00ebrkes\u00ebn n\u00eb nj\u00eb b\u00ebrtham\u00eb. Madje mund t\u00eb tregoni p\u00ebrdoruesve t\u00eb ndrysh\u00ebm k\u00ebt\u00eb konfigurim t\u00eb ndrysh\u00ebm. Prandaj, nuk ka probleme. Dhe ju lutem, p\u00ebrcillni koleg\u00ebve nga Luksoft q\u00eb nuk \u00ebsht\u00eb mir\u00eb q\u00eb nuk gjet\u00ebn k\u00ebt\u00eb p\u00ebrb\u00ebr\u00ebs n\u00eb dokumentacion. <\/p>\n<\/p>\n
Aleks, p\u00ebrsh\u00ebndetje! Doja t\u00eb pyesja nj\u00eb pyetje t\u00eb till\u00eb. Nuk \u00ebsht\u00eb hera e par\u00eb q\u00eb d\u00ebgjoj se shum\u00eb fillojn\u00eb ta p\u00ebrdorin ClickHouse si depo p\u00ebr log-et. N\u00eb raportin tuaj that\u00eb se nuk duhet ta b\u00ebjm\u00eb k\u00ebt\u00eb, pra nuk \u00ebsht\u00eb mir\u00eb t\u00eb ruajm\u00eb rreshta t\u00eb gjat\u00eb. \u00c7far\u00eb mendoni p\u00ebr k\u00ebt\u00eb?<\/em><\/p>\n<\/p>\n
S\u00eb pari, log-et zakonisht nuk jan\u00eb rreshta t\u00eb gjat\u00eb. Natyrisht, ndodhin p\u00ebrjashtime. P\u00ebr shembull, ndonj\u00eb sh\u00ebrbim i shkruar n\u00eb java hedh nj\u00eb exception, dhe ai regjistrohet. Dhe k\u00ebshtu n\u00eb nj\u00eb cik\u00ebl t\u00eb pafund, dhe skadon hap\u00ebsira n\u00eb diskun e fort\u00eb. Zgjidhja \u00ebsht\u00eb shum\u00eb e thjesht\u00eb. N\u00ebse rreshtat jan\u00eb shum\u00eb t\u00eb gjat\u00eb, thjesht prisni ato. Po \u00e7far\u00eb do t\u00eb thot\u00eb t\u00eb gjat\u00eb? Dhjet\u00ebra kilobyte \u2013 \u00ebsht\u00eb e keqe*.<\/p>\n
<\/p>\n
* n\u00eb versionet e reja t\u00eb ClickHouse, \u00ebsht\u00eb aktivizuar "granulimi adaptiv i indeksit", i cili zgjidh kryesisht problemin e ruajtjes s\u00eb vargjeve t\u00eb gjat\u00eb.<\/p>\n
<\/p>\n
Dhe nj\u00eb kilobyte \u2013 \u00ebsht\u00eb n\u00eb rregull?<\/em><\/p>\n<\/p>\n
N\u00eb rregull. <\/p>\n
<\/p>\n
P\u00ebrsh\u00ebndetje! Faleminderit p\u00ebr raportin! Un\u00eb tashm\u00eb e kam pyetur p\u00ebr k\u00ebt\u00eb n\u00eb chat, por nuk e mbaj mend n\u00ebse kam marr\u00eb p\u00ebrgjigje. A \u00ebsht\u00eb planifikuar t\u00eb zgjerohet ndonj\u00ebher\u00eb seksioni WITH n\u00eb m\u00ebnyr\u00ebn e CTE?<\/em><\/p>\n<\/p>\n
Tani p\u00ebr tani jo. Seksioni WITH p\u00ebr ne \u00ebsht\u00eb paksa jo serioz. Ajo \u00ebsht\u00eb si nj\u00eb funksion i vog\u00ebl.<\/p>\n
<\/p>\n
E kuptova. Faleminderit!<\/em><\/p>\n<\/p>\n
Faleminderit p\u00ebr raportin! Shum\u00eb interesante! Nj\u00eb pyetje globale. A \u00ebsht\u00eb planifikuar t\u00eb b\u00ebhet, ndoshta, nj\u00eb modifikim p\u00ebr fshirjen e t\u00eb dh\u00ebnave n\u00eb form\u00ebn e disa z\u00ebvend\u00ebsimeve?<\/em><\/p>\n<\/p>\n
Patjet\u00ebr. Kjo \u00ebsht\u00eb detyra jon\u00eb e par\u00eb n\u00eb list\u00ebn ton\u00eb. Ne tani jemi duke menduar aktivisht se si t\u00eb b\u00ebjm\u00eb gjith\u00e7ka si\u00e7 duhet. Dhe \u00ebsht\u00eb koha p\u00ebr t\u00eb filluar t\u00eb godasim tastier\u00ebn*.<\/p>\n
<\/p>\n
* keni shtypur butonat n\u00eb tastier\u00eb dhe keni b\u00ebr\u00eb gjith\u00e7ka.<\/p>\n
<\/p>\n
A do t\u00eb ket\u00eb ndikim n\u00eb performanc\u00ebn e sistemit apo jo? A do t\u00eb jet\u00eb futja po aq e shpejt\u00eb si tani?<\/em><\/p>\n<\/p>\n
Ndoshta vet\u00eb deletes, vet\u00eb updates do t\u00eb jen\u00eb shum\u00eb t\u00eb r\u00ebnda, por kjo nuk do t\u00eb ndikoje aspak n\u00eb performanc\u00ebn e selects dhe performanc\u00ebn e inserts.<\/p>\n
<\/p>\n
Dhe nj\u00eb pyetje e vog\u00ebl. N\u00eb prezantim p\u00ebrmend\u00ebt p\u00ebr primary key. Pra, kemi partiocionim q\u00eb \u00ebsht\u00eb mujor me default, e sakt\u00eb? Dhe kur vendosim nj\u00eb interval datash q\u00eb bie brenda nj\u00eb muaji, at\u00ebher\u00eb lexojm\u00eb vet\u00ebm k\u00ebt\u00eb partiocion, e sakt\u00eb?<\/em><\/p>\n<\/p>\n
Po.<\/p>\n
<\/p>\n
Nj\u00eb pyetje e till\u00eb. N\u00ebse nuk mund t\u00eb dallojm\u00eb ndonj\u00eb primary key, a \u00ebsht\u00eb e sakt\u00eb t\u00eb b\u00ebhet pik\u00ebrisht n\u00eb fush\u00ebn \"Data\" p\u00ebr t\u00eb pasur nj\u00eb riorganizim m\u00eb t\u00eb vog\u00ebl t\u00eb k\u00ebtyre t\u00eb dh\u00ebnave n\u00eb sfond q\u00eb t\u00eb rregullohen m\u00eb mir\u00eb? N\u00ebse nuk keni k\u00ebrkesa n\u00eb interval dhe as nuk mund t\u00eb zgjidhni ndonj\u00eb \u00e7el\u00ebs primar, a vlen t\u00eb futni dat\u00ebn n\u00eb \u00e7el\u00ebsin primar?<\/em><\/p>\n<\/p>\n
Po.<\/p>\n
<\/p>\n
Ndoshta ka kuptim t\u00eb vendosni n\u00eb \u00e7el\u00ebsin primar nj\u00eb fush\u00eb p\u00ebr t\u00eb cil\u00ebn t\u00eb dh\u00ebnat do t\u00eb comprimojn\u00eb m\u00eb mir\u00eb, n\u00ebse jan\u00eb t\u00eb renditura sipas k\u00ebsaj fushe. P\u00ebr shembull, identifikuesi i p\u00ebrdoruesit. P\u00ebrdoruesi, p\u00ebr shembull, viziton t\u00eb nj\u00ebjtin website. N\u00eb k\u00ebt\u00eb rast vendosni id-n\u00eb e p\u00ebrdoruesit dhe koh\u00ebn. Dhe k\u00ebshtu t\u00eb dh\u00ebnat tuaja do t\u00eb comprimojn\u00eb m\u00eb mir\u00eb. Sa i p\u00ebrket dates, n\u00ebse me t\u00eb v\u00ebrtet\u00eb nuk keni dhe kurr\u00eb nuk keni k\u00ebrkesa n\u00eb interval p\u00ebr datat, at\u00ebher\u00eb mund t\u00eb mos e vendosni dat\u00ebn n\u00eb \u00e7el\u00ebsin primar. <\/p>\n
<\/p>\n
Mir\u00eb, shum\u00eb faleminderit!<\/em><\/p>\nBurimi: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"\u0422\u0430\u043a \u043a\u0430\u043a ClickHouse \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0437\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u043e\u0439, \u043f\u0440\u0438 \u0435\u0433\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0438 \u0432\u0430\u0436\u043d\u043e \u0443\u0447\u0438\u0442\u044b\u0432\u0430\u0442\u044c \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e\u0441\u0442\u0438 \u0435\u0433\u043e \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u044b. \u0412 \u044d\u0442\u043e\u043c \u0434\u043e\u043a\u043b\u0430\u0434\u0435 \u0410\u043b\u0435\u043a\u0441\u0435\u0439 \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0435\u0442 \u043e \u043f\u0440\u0438\u043c\u0435\u0440\u0430\u0445 \u0442\u0438\u043f\u0438\u0447\u043d\u044b\u0445 \u043e\u0448\u0438\u0431\u043e\u043a \u043f\u0440\u0438 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0438 ClickHouse, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0433\u0443\u0442 \u043f\u0440\u0438\u0432\u0435\u0441\u0442\u0438 \u043a \u043d\u0435\u044d\u0444\u0444\u0435\u043a\u0442\u0438\u0432\u043d\u043e\u0439 \u0440\u0430\u0431\u043e\u0442\u0435. \u041d\u0430 \u043f\u0440\u0438\u043c\u0435\u0440\u0430\u0445 \u0438\u0437 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 \u0431\u0443\u0434\u0435\u0442 \u043f\u043e\u043a\u0430\u0437\u0430\u043d\u043e, \u043a\u0430\u043a \u0432\u044b\u0431\u043e\u0440 \u0442\u043e\u0439 \u0438\u043b\u0438 \u0438\u043d\u043e\u0439 \u0441\u0445\u0435\u043c\u044b \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u0434\u0430\u043d\u043d\u044b\u0445 \u043c\u043e\u0436\u0435\u0442 \u0438\u0437\u043c\u0435\u043d\u0438\u0442\u044c \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c \u043d\u0430 \u043f\u043e\u0440\u044f\u0434\u043a\u0438. \u0412\u0441\u0435\u043c \u043f\u0440\u0438\u0432\u0435\u0442! \u041c\u0435\u043d\u044f \u0437\u043e\u0432\u0443\u0442 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":91439,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-91438","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t
![\"P\u00ebrdorim](\"\/wp-content\/uploads\/2020\/08\/8e42c1fffffcc964eacef240ea90bbc5.jpg\")
<\/p>\n