{"id":96515,"date":"2020-10-12T19:43:02","date_gmt":"2020-10-12T17:43:02","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/odyssey-roadmap-chto-eshhyo-my-hotim-ot-pulera-soedinenij-andrej-borodin-2019"},"modified":"2020-10-12T19:43:02","modified_gmt":"2020-10-12T17:43:02","slug":"odyssey-roadmap-chto-eshhyo-my-hotim-ot-pulera-soedinenij-andrej-borodin-2019","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/odyssey-roadmap-chto-eshhyo-my-hotim-ot-pulera-soedinenij-andrej-borodin-2019","title":{"rendered":"Odyssey roadmap: \u00e7far\u00eb tjet\u00ebr d\u00ebshirojm\u00eb nga kolektori i lidhjeve. Andrey Borodin (2019)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Odyssey<\/p>\n

<\/p>\n

N\u00eb raport, Andrei Borodin do t\u00eb flas\u00eb se si ata mor\u00ebn parasysh p\u00ebrvoj\u00ebn e shkall\u00ebzimit t\u00eb PgBouncer gjat\u00eb projektimit t\u00eb pool-it t\u00eb lidhjeve. Odyssey<\/a><\/noindex>, si e vendos\u00ebn at\u00eb n\u00eb prodhim. P\u00ebr m\u00eb tep\u00ebr, do t\u00eb diskutojm\u00eb se cilat funksione t\u00eb pool-it do t\u00eb d\u00ebshironim t\u00eb shihnim n\u00eb versionet e reja: na intereson jo vet\u00ebm t\u00eb mbushim nevojat tona, por t\u00eb zhvillojm\u00eb komunitetin e p\u00ebrdoruesve. Odisea<\/a><\/noindex>.<\/p>\n

<\/a><\/noindex><\/p>\n

Video:<\/p>\n

\n

\r\n \"Luaj\r\n
<\/div>\r\n <\/div><\/center><\/p>\n

\"Odyssey<\/p>\n

<\/p>\n

P\u00ebrsh\u00ebndetje t\u00eb gjith\u00ebve! Un\u00eb quhem Andrei. <\/p>\n

<\/p>\n

\"Odyssey<\/p>\n

<\/p>\n

N\u00eb Yandex, merrem me zhvillimin e bazave t\u00eb t\u00eb dh\u00ebnave open source. Dhe sot tema jon\u00eb \u00ebsht\u00eb p\u00ebr connection pooler-in e lidhjeve. <\/p>\n

<\/p>\n

\"Odyssey<\/p>\n

<\/p>\n

N\u00ebse e dini si t\u00eb em\u00ebrtoni connection pooler-in n\u00eb rusisht, m\u00eb tregoni. Dua shum\u00eb t\u00eb gjej nj\u00eb termin teknik t\u00eb mir\u00eb q\u00eb duhet t\u00eb konsolidohet n\u00eb literatur\u00ebn teknike. <\/p>\n

<\/p>\n

Tema \u00ebsht\u00eb mjaft e nd\u00ebrlikuar, sepse n\u00eb shum\u00eb baza t\u00eb dh\u00ebnash, connection pooler \u00ebsht\u00eb e integruar dhe as nuk \u00ebsht\u00eb nevoja t\u00eb dihet p\u00ebr t\u00eb. Disa konfigurime, sigurisht, ekzistojn\u00eb kudo, por n\u00eb Postgres nuk funksionon k\u00ebshtu. Dhe paralelisht (n\u00eb HighLoad++ 2019) po zhvillohet nj\u00eb prezantim nga Nikolai Samokhvalov p\u00ebr konfigurimin e k\u00ebrkesave n\u00eb Postgres. Dhe kuptoj q\u00eb k\u00ebtu erdh\u00ebn njer\u00ebz q\u00eb tashm\u00eb i kan\u00eb konfiguruar k\u00ebrkesat n\u00eb m\u00ebnyr\u00eb perfekte, dhe k\u00ebta jan\u00eb njer\u00ebz q\u00eb p\u00ebrballen me probleme sistemike m\u00eb t\u00eb rralla, t\u00eb lidhura me rrjetin dhe p\u00ebrdorimin e burimeve. Edhe n\u00eb disa raste mund t\u00eb ket\u00eb qen\u00eb mjaft e komplikuar, n\u00eb kuptimin q\u00eb problemet nuk ishin t\u00eb dukshme.<\/p>\n

<\/p>\n

\"Odyssey<\/p>\n

<\/p>\n

N\u00eb Yandex ka Postgres. N\u00eb Yandex.Cloud jetojn\u00eb shum\u00eb sh\u00ebrbime t\u00eb Yandex-it. Dhe ne kemi disa petabajt t\u00eb dh\u00ebnash, t\u00eb cilat gjenerojn\u00eb jo m\u00eb pak se nj\u00eb milion k\u00ebrkesa n\u00eb sekond\u00eb n\u00eb Postgres. <\/p>\n

<\/p>\n

\"Odyssey<\/p>\n

<\/p>\n

Dhe ne ofrojm\u00eb nj\u00eb klaster mjaft tipik p\u00ebr t\u00eb gjith\u00eb sh\u00ebrbimet \u2013 kjo \u00ebsht\u00eb nodi kryesor primar, dy replika t\u00eb zakonshme (nj\u00eb sinkronike dhe nj\u00eb asinkronike), kopjimi rezerv\u00eb, dhe shkall\u00ebzimi i k\u00ebrkesave lexuese n\u00eb replik\u00eb. <\/p>\n

<\/p>\n

\"Odyssey<\/p>\n

<\/p>\n

\u00c7do nod i klasterit \u00ebsht\u00eb nj\u00eb Postgres, n\u00eb t\u00eb cilin, p\u00ebrve\u00e7 Postgres dhe sistemeve t\u00eb monitorimit, \u00ebsht\u00eb instaluar gjithashtu connection pooler. Connection pooler p\u00ebrdoret p\u00ebr fencing dhe p\u00ebr q\u00ebllimin e tij kryesor. <\/p>\n

<\/p>\n

\"Odyssey<\/p>\n

<\/p>\n

Cila \u00ebsht\u00eb q\u00ebllimi kryesor i connection pooler? <\/p>\n

<\/p>\n

\"Odyssey<\/p>\n

<\/p>\n

N\u00eb Postgres \u00ebsht\u00eb pranuar nj\u00eb model procesi p\u00ebr t\u00eb punuar me baz\u00ebn e t\u00eb dh\u00ebnave. Kjo do t\u00eb thot\u00eb se nj\u00eb lidhje \u00ebsht\u00eb nj\u00eb proces, nj\u00eb backend Postgres. Dhe n\u00eb k\u00ebt\u00eb backend ka shum\u00eb cache t\u00eb ndryshme, t\u00eb cilat jan\u00eb mjaft t\u00eb kushtueshme p\u00ebr t'u b\u00ebr\u00eb t\u00eb ndryshme p\u00ebr lidhje t\u00eb ndryshme. <\/p>\n

<\/p>\n

\"Odyssey<\/p>\n

<\/p>\n

P\u00ebr m\u00eb tep\u00ebr, n\u00eb kodin e Postgres ka nj\u00eb masiv, i quajtur procArray. Ai p\u00ebrmban t\u00eb dh\u00ebna kryesore mbi lidhjet rrjet\u00ebrore. Dhe pothuajse t\u00eb gjitha algorithmet q\u00eb trajtojn\u00eb procArray kan\u00eb komplekse lineare, ata kalojn\u00eb p\u00ebrmes gjith\u00eb masivit t\u00eb lidhjeve rrjet\u00ebrore. Kjo \u00ebsht\u00eb nj\u00eb cik\u00ebl mjaft i shpejt\u00eb, por me numrin e madh t\u00eb lidhjeve rrjet\u00ebrore hyr\u00ebse, gjith\u00e7ka b\u00ebhet paksa m\u00eb e shtrenjt\u00eb. Dhe kur gjith\u00e7ka b\u00ebhet pak m\u00eb e shtrenjt\u00eb, n\u00eb fund mund t\u00eb paguani nj\u00eb \u00e7mim shum\u00eb t\u00eb lart\u00eb p\u00ebr numrin e madh t\u00eb lidhjeve rrjet\u00ebrore. <\/p>\n

<\/p>\n

\"Odyssey<\/p>\n

<\/p>\n

Ekzistojn\u00eb 3 qasje t\u00eb mundshme:<\/p>\n

<\/p>\n