{"id":36157,"date":"2019-10-31T22:09:55","date_gmt":"2019-10-31T19:09:55","guid":{"rendered":"https:\/\/prohoster.info\/blog\/skolko-tps-v-vashem-blokchejne\/"},"modified":"2019-10-31T22:09:55","modified_gmt":"2019-10-31T19:09:55","slug":"skolko-tps-v-vashem-blokchejne","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/skolko-tps-v-vashem-blokchejne","title":{"rendered":"Sa sajtet TPS n\u00eb bllokad\u00ebn tuaj?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Pyetja m\u00eb e zakonshme p\u00ebr \u00e7do sistem t\u00eb distribuuar nga nj\u00eb specialist jo teknik \u00ebsht\u00eb \u201cSa tps ka bllokada juaj?\u201d. Megjithat\u00eb, numri i dh\u00ebn\u00eb n\u00eb p\u00ebrgjigje zakonisht ka pak t\u00eb b\u00ebj\u00eb me at\u00eb q\u00eb d\u00ebshiron t\u00eb d\u00ebgjoj\u00eb pyet\u00ebsi. N\u00eb t\u00eb v\u00ebrtet\u00eb, ai d\u00ebshiron t\u00eb pyes\u00eb \u201ca p\u00ebrshtatet bllokada juaj me k\u00ebrkesat e mia t\u00eb biznesit\u201d, dhe k\u00ebto k\u00ebrkesa nuk jan\u00eb nj\u00eb num\u00ebr e vetme, por nj\u00eb grup kushtesh \u2014 k\u00ebtu p\u00ebrfshihet q\u00ebndrueshm\u00ebria e rrjetit, k\u00ebrkesat p\u00ebr p\u00ebrfundim, madh\u00ebsit\u00eb, natyra e transaksioneve dhe shum\u00eb parametra t\u00eb tjer\u00eb. K\u00ebshtu q\u00eb p\u00ebrgjigjja n\u00eb pyetjen \u201csa tps\u201d nganj\u00ebher\u00eb do t\u00eb jet\u00eb e komplikuar dhe pothuajse kurr\u00eb nuk do t\u00eb jet\u00eb e plot\u00eb. Nj\u00eb sistem i distribuuar me dhjet\u00ebra dhe qindra nyjash q\u00eb realizojn\u00eb llogaritje t\u00eb nd\u00ebrlikuara mund t\u00eb jet\u00eb n\u00eb nj\u00eb s\u00ebr\u00eb gjendjesh t\u00eb ndryshme, t\u00eb lidhura me gjendjen e rrjetit, p\u00ebrmbajtjen e bllokad\u00ebs, d\u00ebshtimet teknike, problemet ekonomike, sulmet n\u00eb rrjet dhe shum\u00eb arsye t\u00eb tjera. Faza n\u00eb t\u00eb cilat mund t\u00eb ket\u00eb probleme me performanc\u00ebn dallohen nga sh\u00ebrbimet tradicionale, dhe serveri i rrjetit t\u00eb bllokadave \u00ebsht\u00eb nj\u00eb sh\u00ebrbim rrjeti q\u00eb kombinon funksionalitetin e nj\u00eb baze t\u00eb dh\u00ebnash, serveri web dhe klient torrent, gj\u00eb q\u00eb e b\u00ebn jasht\u00ebzakonisht t\u00eb nd\u00ebrlikuar n\u00eb aspektin e profilit t\u00eb ngarkes\u00ebs n\u00eb t\u00eb gjitha n\u00ebn-sistemat: procesori, memoria, rrjeti, ruajtja.<\/p>\n

<\/p>\n

Si\u00e7 ndodhi, rrjetet e decentralizuara dhe bllokadat jan\u00eb nj\u00eb software mjaft specifik dhe i pazakont\u00eb p\u00ebr zhvilluesit e software-ve t\u00eb centralizuar. Prandaj, do t\u00eb doja t\u00eb theksoj aspektet e r\u00ebnd\u00ebsishme t\u00eb performanc\u00ebs dhe q\u00ebndrueshm\u00ebris\u00eb s\u00eb rrjeteve t\u00eb decentralizuara, qasjet p\u00ebr matjen e tyre dhe identifikimin e pengesave. Ne do t\u00eb shqyrtojm\u00eb probleme t\u00eb ndryshme t\u00eb performanc\u00ebs q\u00eb kufizojn\u00eb shpejt\u00ebsin\u00eb e sh\u00ebrbimit p\u00ebr p\u00ebrdoruesit e bllokadave dhe do t\u00eb sh\u00ebnojm\u00eb karakteristikat q\u00eb jan\u00eb specifike p\u00ebr k\u00ebt\u00eb lloj software-i.<\/p>\n

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

Fazat e k\u00ebrkes\u00ebs p\u00ebr sh\u00ebrbim nga klienti i bllokad\u00ebs<\/h2>\n

<\/p>\n

P\u00ebr t\u00eb folur me sinqeritet p\u00ebr cil\u00ebsin\u00eb e \u00e7do sh\u00ebrbimi m\u00eb shum\u00eb se pak t\u00eb komplikuar, duhet t\u00eb merret parasysh jo vet\u00ebm vlerat mesatare, por edhe ato maksimale\/minimale, medianat dhe percentilet. Teoretikisht, mund t\u00eb flitet p\u00ebr 1000 tps n\u00eb ndonj\u00eb bllokshit, por n\u00ebse 900 transaksione jan\u00eb realizuar me nj\u00eb shpejt\u00ebsi t\u00eb madhe, nd\u00ebrsa 100 kan\u00eb 'shkuar n\u00eb ngadal\u00ebsi' p\u00ebr disa sekonda, at\u00ebher\u00eb koha mesatare e mbledhur nga t\u00eb gjitha transaksionet nuk \u00ebsht\u00eb nj\u00eb metrik\u00eb e drejt\u00eb p\u00ebr klientin, i cili p\u00ebr disa sekonda nuk arriti t\u00eb p\u00ebrfundoj\u00eb transaksionin. 'Gropat' temporale, t\u00eb shkaktuara nga humbja e rrethave t\u00eb konsensusit ose ndarjes s\u00eb rrjetit, mund t\u00eb d\u00ebmtojn\u00eb shum\u00eb sh\u00ebrbimin, i cili n\u00eb stendat testuese tregoi nj\u00eb performanc\u00eb t\u00eb shk\u00eblqyer.<\/p>\n

<\/p>\n

P\u00ebr t\u00eb identifikuar k\u00ebto bottlenecks \u00ebsht\u00eb e nevojshme t\u00eb kuptohet mir\u00eb fazat se kur nj\u00eb blockchain real mund t\u00eb has\u00eb v\u00ebshtir\u00ebsi n\u00eb sh\u00ebrbimin e p\u00ebrdoruesve. Le t\u00eb p\u00ebrshkruajm\u00eb ciklin e dor\u00ebzimit dhe procesin e p\u00ebrpunimit t\u00eb transaksioneve, si dhe marrjen e gjendjes s\u00eb re t\u00eb blockchain-it, nga e cila klienti mund t\u00eb konfirmoj\u00eb q\u00eb transaksioni i tij \u00ebsht\u00eb p\u00ebrpunuar dhe regjistruar.<\/p>\n

<\/p>\n

    \n
  1. transaksioni formohet n\u00eb klient<\/li>\n
  2. transaksioni n\u00ebnshkruhet n\u00eb klient<\/li>\n
  3. klienti zgjedh nj\u00eb nga nodet dhe i d\u00ebrgon transaksionin e tij<\/li>\n
  4. klienti regjistrohet p\u00ebr azhornimet e state database-it t\u00eb nodit, duke pritur shfaqjen e rezultateve t\u00eb p\u00ebrpunimit t\u00eb transaksionit t\u00eb tij<\/li>\n
  5. noda shp\u00ebrndan transaksionin n\u00eb rrjetin p2p<\/li>\n
  6. disa, ose nj\u00eb BP (prodhues bllokesh) procesojn\u00eb transaksionet e akumuluara, duke azhurnuar state database<\/li>\n
  7. BP formon nj\u00eb bllok t\u00eb ri, duke p\u00ebrpunuar numrin e nevojsh\u00ebm t\u00eb transaksioneve<\/li>\n
  8. BP shp\u00ebrndan bllokun e ri n\u00eb rrjetin p2p<\/li>\n
  9. blloku i ri d\u00ebrgohet n\u00eb nod\u00ebn q\u00eb kliente i drejtohet<\/li>\n
  10. noda azhurnon state database<\/li>\n
  11. noda sheh azhurnimin q\u00eb i p\u00ebrket klientit dhe i d\u00ebrgon atij nj\u00eb njoftim p\u00ebr transaksionin<\/li>\n<\/ol>\n

    <\/p>\n

    Tani le ta nj\u00ebher\u00eb n\u00eb detaje k\u00ebto etapa dhe t\u00eb p\u00ebrshkruajm\u00eb problemet potenciale me performanc\u00ebn n\u00eb \u00e7do hap. Ndryshe nga sistemet e centralizuara, ne do t\u00eb shqyrtojm\u00eb gjithashtu ekzekutimin e kodit n\u00eb klient\u00ebt e rrjetit. Mjaft shpesh, kur matet tps, koha e procesimit t\u00eb transaksioneve mblidhet nga nodet dhe jo nga klienti \u2014 kjo nuk \u00ebsht\u00eb krejt\u00ebsisht e sinqert\u00eb. Klienti nuk e ka problem sa shpejt node proceson transaksionin e tij, ajo q\u00eb \u00ebsht\u00eb m\u00eb e r\u00ebnd\u00ebsishme p\u00ebr t\u00eb \u00ebsht\u00eb momenti kur informacioni i sakt\u00eb mbi k\u00ebt\u00eb transaksion, i p\u00ebrfshir\u00eb n\u00eb blockchain, do t\u00eb jet\u00eb n\u00eb dispozicion p\u00ebr t\u00eb. Kjo metrik\u00eb \u00ebsht\u00eb esencialisht koha e ekzekutimit t\u00eb transaksionit. Kjo do t\u00eb thot\u00eb se klient\u00ebt e ndrysh\u00ebm, edhe pse d\u00ebrgojn\u00eb nj\u00eb transaksion t\u00eb nj\u00ebjt\u00eb, mund t\u00eb ken\u00eb koh\u00eb t\u00ebr\u00ebsisht t\u00eb ndryshme, t\u00eb cilat varen nga kanali, ngarkesa dhe af\u00ebrsia e nodit, etj. Pra, \u00ebsht\u00eb thelb\u00ebsore t\u00eb matet kjo koh\u00eb n\u00eb klient\u00eb, pasi ky \u00ebsht\u00eb parametri q\u00eb duhet optimizuar.<\/p>\n

    <\/p>\n

    P\u00ebrgatitja e transaksionit nga ana e klientit<\/h2>\n

    <\/p>\n

    Le t\u00eb fillojm\u00eb me dy pik\u00ebt e para: transaksioni formohet dhe n\u00ebnshkruhet nga klienti. Si\u00e7 duket, kjo gjithashtu mund t\u00eb jet\u00eb nj\u00eb ngushtic\u00eb e performanc\u00ebs s\u00eb blockchain nga perspektiva e klientit. Kjo \u00ebsht\u00eb e pazakont\u00eb p\u00ebr sh\u00ebrbimet e centralizuara, t\u00eb cilat i marrin p\u00ebr vete t\u00eb gjitha llogarit\u00eb dhe operacionet me t\u00eb dh\u00ebna, nd\u00ebrsa klienti p\u00ebrgatit nj\u00eb k\u00ebrkes\u00eb t\u00eb shkurt\u00ebr, e cila mund t\u00eb k\u00ebrkoj\u00eb nj\u00eb volum t\u00eb madh t\u00eb dh\u00ebnash ose llogaritjesh, duke marr\u00eb rezultatin e gatsh\u00ebm. N\u00eb blockchain, kodi i klientit po b\u00ebhet gjithnj\u00eb e m\u00eb i fuqish\u00ebm, nd\u00ebrsa b\u00ebrthama e blockchain-it po b\u00ebhet gjithnj\u00eb e m\u00eb e leht\u00eb, dhe detyrat masive t\u00eb llogaritjes zakonisht u jepen softuer\u00ebve t\u00eb klientit. N\u00eb blockchain ekzistojn\u00eb klient\u00eb q\u00eb mund t\u00eb p\u00ebrgatisin nj\u00eb transaksion p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb (po flas p\u00ebr d\u00ebshmit\u00eb e ndryshme merkle, d\u00ebshmit\u00eb e shkurt\u00ebra, n\u00ebnshkrimet threshold dhe operacione t\u00eb tjera komplekse nga ana e klientit). Nj\u00eb shembull i mir\u00eb i verifikimit t\u00eb leht\u00eb on-chain dhe p\u00ebrgatitjes s\u00eb r\u00ebnd\u00eb t\u00eb transaksionit nga ana e klientit \u00ebsht\u00eb d\u00ebshmia e p\u00ebrkat\u00ebsis\u00eb n\u00eb nj\u00eb list\u00eb t\u00eb bazuar n\u00eb Merkle-tree, ja artikulli<\/a><\/noindex>.<\/p>\n

    <\/p>\n

    Po gjithashtu, nuk duhet harruar se kodi i klientit nuk d\u00ebrgon thjesht transaksione n\u00eb blockchain, por fillimisht k\u00ebrkon gjendjen e blockchain-it \u2014 dhe kjo aktivitet mund t\u00eb ndikoj\u00eb n\u00eb ngarkes\u00ebn e rrjetit dhe node-ve t\u00eb blockchain-it. Prandaj, gjat\u00eb marrjes s\u00eb matjeve, do t\u00eb ishte e arsyeshme t\u00eb emuloni sa m\u00eb sakt\u00eb t\u00eb jet\u00eb e mundur sjelljen e kodit t\u00eb klientit. Edhe n\u00ebse n\u00eb blockchain-in tuaj ka klient\u00eb normal\u00eb t\u00eb leht\u00eb, q\u00eb vendosin nj\u00eb n\u00ebnshkrim dixhital t\u00eb zakonsh\u00ebm n\u00eb nj\u00eb transaksion t\u00eb thjesht\u00eb p\u00ebr transferimin e ndonj\u00eb asset-i, sasia e llogaritjeve n\u00eb an\u00ebn e klientit vazhdon t\u00eb rritet \u00e7do vit, algoritmet kriptografike po b\u00ebhen m\u00eb t\u00eb forta, dhe kjo pjes\u00eb e procesimit mund t\u00eb shnd\u00ebrrohet n\u00eb nj\u00eb bllokim t\u00eb konsideruesh\u00ebm n\u00eb t\u00eb ardhmen. Prandaj, jini t\u00eb kujdessh\u00ebm dhe mos e humbisni situat\u00ebn kur n\u00eb nj\u00eb transaksion q\u00eb zgjat 3.5 sekonda, 2.5 sekonda shpenzohen p\u00ebr p\u00ebrgatitjen dhe n\u00ebnshkrimin e transaksionit, dhe 1.0 sekond\u00eb p\u00ebr d\u00ebrgimin n\u00eb rrjet dhe pritjen e p\u00ebrgjigjes. P\u00ebr t\u00eb vler\u00ebsuar rreziqet e ndodhjes s\u00eb k\u00ebtij bllokimi, duhet t\u00eb mblidhni metrika nga makinat e klient\u00ebve dhe jo vet\u00ebm nga node-t e blockchain-it.<\/p>\n

    <\/p>\n

    D\u00ebrgimi i transaksionit dhe monitorimi i statusit t\u00eb tij<\/h2>\n

    <\/p>\n

    Hapi i ardhsh\u00ebm \u00ebsht\u00eb d\u00ebrgimi i transaksionit n\u00eb node-n e zgjedhur t\u00eb blockchain-it dhe marrja e statusit p\u00ebr pranimin e tij n\u00eb grupin e transaksioneve. Ky hap i ngjan nj\u00eb k\u00ebrkese t\u00eb zakonshme n\u00eb nj\u00eb databaz\u00eb; node-ja duhet t\u00eb regjistroj\u00eb transaksionin n\u00eb grupin dhe t\u00eb filloj\u00eb t\u00eb shp\u00ebrndaj\u00eb informacionin p\u00ebr t\u00eb n\u00eb rrjetin p2p. Qasja p\u00ebr vler\u00ebsimin e performanc\u00ebs k\u00ebtu \u00ebsht\u00eb e ngjashme me vler\u00ebsimin e pun\u00ebs s\u00eb mikrosh\u00ebrbimeve tradicionale Web API, nd\u00ebrsa vet\u00eb transaksionet n\u00eb blockchain mund t\u00eb p\u00ebrdit\u00ebsohen, duke ndryshuar statusin aktivisht. N\u00eb p\u00ebrgjith\u00ebsi, p\u00ebrdit\u00ebsimi i informacionit p\u00ebr nj\u00eb transaksion n\u00eb disa blockchain-e mund t\u00eb ndodh\u00eb disa her\u00eb, p\u00ebr shembull, gjat\u00eb kalimeve mes bifurkime t\u00eb zinxhirit ose kur BP njoftojn\u00eb se kan\u00eb p\u00ebr q\u00ebllim t\u00eb p\u00ebrfshijn\u00eb transaksionin n\u00eb bllok. Kufizimet mbi volumet e k\u00ebtij grupi dhe numrin e transaksioneve n\u00eb t\u00eb mund t\u00eb ndikojn\u00eb n\u00eb performanc\u00ebn e blockchain-it. N\u00ebse grupi i transaksioneve \u00ebsht\u00eb mbushur deri n\u00eb madh\u00ebsin\u00eb maksimale t\u00eb mundshme, ose nuk i p\u00ebrshtatet n\u00eb memorjen e p\u00ebrkohshme - performanca e rrjetit mund t\u00eb bjer\u00eb ndjesh\u00ebm. Blockchain-et nuk kan\u00eb mjete t\u00eb centralizuara mbrojtjeje nga fluksi i mesazheve t\u00eb plehrave, dhe n\u00ebse blockchain-i mb\u00ebshtet transaksione t\u00eb volumit t\u00eb madh me tarifa t\u00eb ul\u00ebta, kjo mund t\u00eb \u00e7oj\u00eb n\u00eb mbushjen e grupit t\u00eb transaksioneve - ky \u00ebsht\u00eb nj\u00eb tjet\u00ebr bllokim potencial i performanc\u00ebs.<\/p>\n

    <\/p>\n

    N\u00eb bllokshitet, klienti d\u00ebrgon nj\u00eb transaksion n\u00eb \u00e7do nod t\u00eb bllokshit q\u00eb i p\u00eblqen, hash-i i transaksionit zakonisht do t\u00eb jet\u00eb i njohur p\u00ebr klientin q\u00eb para d\u00ebrgimit, k\u00ebshtu q\u00eb gjith\u00e7ka q\u00eb i nevojitet \u00ebsht\u00eb t\u00eb arrij\u00eb nj\u00eb lidhje dhe pas d\u00ebrgimit t\u00eb pres\u00eb kur bllokshitet t\u00eb ndryshoj\u00eb gjendjen e tij, duke p\u00ebrfshir\u00eb transaksionin e tij. Vlen t\u00eb theksohet se duke matur 'tps' mund t\u00eb p\u00ebrftohen rezultate krejt\u00ebsisht t\u00eb ndryshme p\u00ebr m\u00ebnyra t\u00eb ndryshme lidhjeje me nodin e bllokshit. Kjo mund t\u00eb jet\u00eb nj\u00eb RPC HTTP normal ose WebSocket, e cila lejon realizimin e modelit 'subscribe'. N\u00eb rastin e dyt\u00eb, klienti do t\u00eb marr\u00eb njoftimin m\u00eb her\u00ebt, dhe noud do t\u00eb shpenzoj\u00eb m\u00eb pak burime (kryesisht memorie dhe trafik) p\u00ebr p\u00ebrgjigjet n\u00eb lidhje me gjendjen e transaksionit. Pra, kur matet 'tps', \u00ebsht\u00eb e nevojshme t\u00eb merren parasysh m\u00ebnyrat e lidhjes s\u00eb klient\u00ebve me nodet. P\u00ebr k\u00ebt\u00eb arsye, p\u00ebr t\u00eb vler\u00ebsuar rreziqet e shfaqjes s\u00eb k\u00ebtij bottleneck-u, benchmark-u i bllokshit duhet t\u00eb mund t\u00eb emuloj klient\u00eb dhe me WebSocket dhe me k\u00ebrkesa HTTP RPC, n\u00eb proporcione q\u00eb p\u00ebrputhen me rrjetet reale, si dhe t\u00eb ndryshoj\u00eb natyr\u00ebn dhe madh\u00ebsin\u00eb e transaksioneve.<\/p>\n

    <\/p>\n

    P\u00ebr vler\u00ebsimin e rreziqeve t\u00eb shfaqjes s\u00eb k\u00ebtij bottleneck-u \u00ebsht\u00eb gjithashtu e nevojshme t\u00eb mblidhni metrika nga makinat e klient\u00ebve, dhe jo vet\u00ebm nga nodat e blockchain-it.<\/p>\n

    <\/p>\n

    Transferimi i transaksioneve dhe blloqeve p\u00ebrmes rrjetit p2p<\/h2>\n

    <\/p>\n

    N\u00eb blockchain-e, p\u00ebr transferimin mes pjes\u00ebmarr\u00ebsve t\u00eb transaksioneve dhe blloqeve p\u00ebrdoret rrjet\u00ebzim peer-to-peer (p2p). Transaksionet shp\u00ebrndahen n\u00eb rrjet, duke filluar nga nj\u00eb nga nodet, derisa t\u00eb arrijn\u00eb peer-at-produes t\u00eb blloqeve, t\u00eb cil\u00ebt paketojn\u00eb transaksionet n\u00eb blloqe dhe, duke p\u00ebrdorur t\u00eb nj\u00ebjtin p2p, shp\u00ebrndajn\u00eb blloqet e reja n\u00eb t\u00eb gjitha nodat e rrjetit. Baza e shumic\u00ebs s\u00eb rrjeteve moderne p2p \u00ebsht\u00eb ndryshime t\u00eb ndryshme t\u00eb protokollit Kademlia. Ja<\/a><\/noindex> nj\u00eb p\u00ebrmbledhje e shkurt\u00ebr e k\u00ebtij protokolli, dhe ja<\/a><\/noindex> \u2014 nj\u00eb artikull me matje t\u00eb ndryshme n\u00eb rrjetin BitTorrent, nga i cili mund t\u00eb kuptoni \u2014 se ky lloj rrjeti \u00ebsht\u00eb m\u00eb i komplikuar, dhe m\u00eb pak i parashikuesh\u00ebm se sa nj\u00eb rrjet i konfiguruar fort me nj\u00eb sh\u00ebrbim t\u00eb centralizuar. Gjithashtu, ja<\/a><\/noindex> nj\u00eb artikull mbi matjen e metrikave t\u00eb ndryshme interesante p\u00ebr nodat Ethereum.<\/p>\n

    <\/p>\n

    N\u00eb thelb, \u00e7do peer n\u00eb k\u00ebto rrjete mban list\u00ebn e vet dinamike t\u00eb peers t\u00eb tjer\u00eb, nga t\u00eb cil\u00ebt k\u00ebrkon blloqet e informacionit q\u00eb i adresohen sipas p\u00ebrmbajtjes. Kur merr nj\u00eb k\u00ebrkes\u00eb, peer ose jep informacionin e nevojsh\u00ebm, ose e transmeton k\u00ebrkes\u00ebn te nj\u00eb peer tjet\u00ebr pseudopasur nga lista, dhe pasi merr p\u00ebrgjigjen, ia kalon at\u00eb k\u00ebrkuesit dhe p\u00ebr nj\u00eb periudh\u00eb t\u00eb caktuar e ruan n\u00eb cache, duke e ofruar k\u00ebt\u00eb bllok informacioni m\u00eb her\u00ebt her\u00ebn tjet\u00ebr. K\u00ebshtu, informacioni popullor gjendet n\u00eb nj\u00eb num\u00ebr t\u00eb madh cache-esh te nj\u00eb num\u00ebr t\u00eb madh peers, nd\u00ebrsa ai jo-popullor gradualisht z\u00ebvend\u00ebsohet. Peers mbajn\u00eb nj\u00eb llogari se kush i kalon sa informacion, dhe rrjeti p\u00ebrpiqet t\u00eb stimuloj\u00eb ata q\u00eb shp\u00ebrndajn\u00eb aktivisht, duke rritur renditjen e tyre dhe duke u siguruar nj\u00eb nivel m\u00eb t\u00eb lart\u00eb sh\u00ebrbimi, duke p\u00ebrjashtuar automatikisht pjes\u00ebmarr\u00ebsit inaktiv\u00eb nga listat e peers.<\/p>\n

    <\/p>\n

    Pra ndaj, tani transaksioni duhet t\u00eb shp\u00ebrndahet n\u00eb rrjet, q\u00eb t\u00eb shihet nga block-producer-\u00ebt dhe t\u00eb p\u00ebrfshihet n\u00eb bllok. Noda aktivisht \"ndan\" transaksionin e ri me t\u00eb gjith\u00eb ata q\u00eb d\u00ebshirojn\u00eb dhe d\u00ebgjon rrjetin, duke pritur bllokun, n\u00eb indeksin e t\u00eb cilit do t\u00eb shfaqet transaksioni i k\u00ebrkuar, p\u00ebr t\u00eb njoftuar klientin q\u00eb po pret. Koha nd\u00ebrmjet q\u00eb rrjeti kalon informacionin p\u00ebr transaksionet dhe blloqet e reja n\u00eb rrug\u00ebt p2p varet nga shum\u00eb faktor\u00eb: numri i nod\u00ebve t\u00eb ndersh\u00ebm q\u00eb punojn\u00eb af\u00ebr (nga pik\u00ebpamja rrjetit), \"ngrohja\" e cache-ve t\u00eb k\u00ebtyre nod\u00ebve, madh\u00ebsia e blloqeve, transaksioneve, natyra e ndryshimeve, gjeografia e rrjetit, numri i nod\u00ebve dhe shum\u00eb faktor\u00eb t\u00eb tjer\u00eb. Matjet komplekse t\u00eb metrikave t\u00eb performanc\u00ebs n\u00eb k\u00ebto rrjete \u2014 jan\u00eb nj\u00eb \u00e7\u00ebshtje e nd\u00ebrlikuar, dhe \u00ebsht\u00eb e nevojshme t\u00eb vler\u00ebsohen nj\u00ebkoh\u00ebsisht koha e p\u00ebrpunimit t\u00eb k\u00ebrkesave si n\u00eb klient\u00eb ashtu edhe n\u00eb peer-a (nod\u00ebt e blockchain-it). Problemet n\u00eb ndonj\u00eb mekaniz\u00ebm p2p, nxitja e gabuar dhe keqmenaxhimi i t\u00eb dh\u00ebnave, menaxhimi joefikas i listave t\u00eb peer-ve aktiv\u00eb dhe shum\u00eb faktor\u00eb t\u00eb tjer\u00eb mund t\u00eb jen\u00eb shkak p\u00ebr vonesa q\u00eb ndikojn\u00eb n\u00eb efikasitetin e gjith\u00eb rrjetit, dhe ky bottleneck \u00ebsht\u00eb m\u00eb e v\u00ebshtir\u00eb p\u00ebr t'u analizuar, testuar dhe interpretuar rezultatet.<\/p>\n

    <\/p>\n

    Procesimi i zinxhirit t\u00eb blloqeve dhe p\u00ebrdit\u00ebsimi i databaz\u00ebs s\u00eb gjendjes<\/h2>\n

    <\/p>\n

    Pjesa m\u00eb e r\u00ebnd\u00ebsishme e funksionit t\u00eb blockchain-it \u00ebsht\u00eb algoritmi i konsensusit, zbatimi i tij n\u00eb blloqet e reja, t\u00eb marra nga rrjeti dhe p\u00ebrpunimi i transaksioneve me regjistrimin e rezultateve n\u00eb databaz\u00ebn e gjendjes. Shtimi i nj\u00eb blloku t\u00eb ri n\u00eb zinxhir dhe zgjedhja q\u00eb i ndjek zinxhirit kryesor duhet t\u00eb funksionoj\u00eb sa m\u00eb shpejt. Megjithat\u00eb, n\u00eb jet\u00ebn reale \"duhet\" nuk do t\u00eb thot\u00eb \"funksionon\", dhe mund t\u00eb imagjinoni nj\u00eb situat\u00eb kur dy zinxhir\u00eb konkurrues t\u00eb gjat\u00eb nd\u00ebrruar vazhdimisht, duke ndryshuar metadatat e mij\u00ebra transaksioneve n\u00eb pool me \u00e7do nd\u00ebrrim dhe duke shkaktuar rikthime t\u00eb vazhdueshme t\u00eb gjendjes s\u00eb databaz\u00ebs s\u00eb gjendjes. Ky etap, n\u00eb planin e p\u00ebrcaktimit t\u00eb bottleneck-ut \u00ebsht\u00eb m\u00eb i leht\u00eb se shtresa rrjet\u00ebrore p2p, pasi ekzekutimi i transaksioneve dhe algoritmi i konsensusit jan\u00eb t\u00eb determinuara, dhe \u00ebsht\u00eb m\u00eb e leht\u00eb t\u00eb mat\u00ebsh di\u00e7ka k\u00ebtu.
    \nE r\u00ebnd\u00ebsishme \u00ebsht\u00eb t\u00eb mos ngat\u00ebrrohet degradimi rast\u00ebsor i performanc\u00ebs n\u00eb k\u00ebt\u00eb faz\u00eb me problemet n\u00eb rrjet \u2014 nodet japin m\u00eb ngadal\u00eb blloqe dhe informacion rreth zinxhirit kryesor dhe p\u00ebr klientin e jasht\u00ebm, k\u00ebt\u00eb mund ta duket si nj\u00eb rrjet i ngadalsh\u00ebm, ndon\u00ebse problemi ndodhet krejt\u00ebsisht n\u00eb nj\u00eb vend tjet\u00ebr.<\/p>\n

    <\/p>\n

    P\u00ebr optimizimin e performanc\u00ebs n\u00eb k\u00ebt\u00eb faz\u00eb, \u00ebsht\u00eb e dobishme t\u00eb mblidhen dhe monitorohen metrikat nga vet\u00eb nodet dhe t\u00eb p\u00ebrfshihen ato q\u00eb lidhen me p\u00ebrdit\u00ebsimin e baz\u00ebs s\u00eb t\u00eb dh\u00ebnave t\u00eb shtetit: numri i blloqeve t\u00eb procesuar n\u00eb nod, madh\u00ebsia e tyre, numri i transaksioneve, numri i alternimeve midis bifurkave t\u00eb zinxhirit, numri i blloqeve t\u00eb pavlefshme, koha e funksionimit t\u00eb makineris\u00eb virtuale, koha e regjistrimit t\u00eb t\u00eb dh\u00ebnave dhe t\u00eb tjera. Kjo do t\u00eb ndihmoj\u00eb p\u00ebr t\u00eb mos ngat\u00ebrruar problemet rrjetore me gabimet n\u00eb algoritmet e procesimit t\u00eb zinxhir\u00ebve.<\/p>\n

    <\/p>\n

    Makina virtuale q\u00eb proceson transaksionet mund t\u00eb jet\u00eb nj\u00eb burim i dobish\u00ebm informacioni q\u00eb mund t\u00eb optimizoj\u00eb funksionimin e blockchain-it. Sasia e alokimeve t\u00eb memories, numri i instrukcioneve read\/write dhe metrika t\u00eb tjera q\u00eb lidhen me efikasitetin e ekzekutimit t\u00eb kodit t\u00eb kontratave mund t\u00eb japin shum\u00eb informacion t\u00eb dobish\u00ebm p\u00ebr zhvilluesit. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, kontratat inteligjente jan\u00eb programe dhe prandaj n\u00eb teori ato mund t\u00eb konsumojn\u00eb \u00e7do burim: cpu\/memory\/network\/storage, k\u00ebshtu q\u00eb procesimi i transaksioneve \u00ebsht\u00eb nj\u00eb faz\u00eb mjaft e pasigurt, e cila gjithashtu ndryshon ndjesh\u00ebm gjat\u00eb kalimit midis versioneve dhe gjat\u00eb ndryshimit t\u00eb kodit t\u00eb kontratave. Prandaj, metrikat q\u00eb lidhen me procesimin e transaksioneve jan\u00eb gjithashtu t\u00eb nevojshme p\u00ebr optimizimin e efektivitetit t\u00eb performanc\u00ebs s\u00eb blockchain-it.<\/p>\n

    <\/p>\n

    Marrja e njoftimit nga klienti p\u00ebr aktivizimin e transaksionit n\u00eb blockchain<\/h2>\n

    <\/p>\n

    Ky \u00ebsht\u00eb faza p\u00ebrfundimtare e marrjes s\u00eb sh\u00ebrbimit nga klienti i blockchain-it, n\u00eb krahasim me fazat e tjera, k\u00ebtu nuk ka shpenzime t\u00eb m\u00ebdha, por akoma duhet marr\u00eb parasysh mund\u00ebsia e marrjes s\u00eb nj\u00eb p\u00ebrgjigjeje voluminoze nga nodi (p\u00ebr shembull, nj\u00eb smart kontrat\u00eb q\u00eb kthej\u00eb nj\u00eb array t\u00eb dh\u00ebnash). N\u00eb \u00e7do rast, ky moment \u00ebsht\u00eb m\u00eb i r\u00ebnd\u00ebsish\u00ebm p\u00ebr at\u00eb q\u00eb i ka b\u00ebr\u00eb pyetje \"sa tps ka blockchain-i juaj?\" sepse n\u00eb k\u00ebt\u00eb moment regjistrohet koha e marrjes s\u00eb sh\u00ebrbimit. <\/p>\n

    <\/p>\n

    N\u00eb k\u00ebt\u00eb pik\u00eb \u00ebsht\u00eb e nevojshme t\u00eb d\u00ebrgohet koha totale q\u00eb i \u00ebsht\u00eb dashur klientit p\u00ebr t\u00eb pritur p\u00ebrgjigjen nga blockchain-i, kjo \u00ebsht\u00eb koha q\u00eb p\u00ebrdoruesi do t\u00eb pres\u00eb p\u00ebr t\u00eb marr\u00eb konfirmimin n\u00eb aplikacionin e tij, dhe optimizimi i saj \u00ebsht\u00eb detyra kryesore e zhvilluesve.<\/p>\n

    <\/p>\n

    P\u00ebrfundim<\/h1>\n

    <\/p>\n

    Si rezultat, mund t\u00eb p\u00ebrshkruhen llojet e operacioneve q\u00eb kryhen n\u00eb blockchain dhe t'i ndahen n\u00eb disa kategori:<\/p>\n

    <\/p>\n

      \n
    1. transformime kriptografike, nd\u00ebrtimi i provave<\/li>\n
    2. networking peer-to-peer, replikimi i transaksioneve dhe blloqeve<\/li>\n
    3. procesimi i transaksioneve, ekzekutimi i kontratave inteligjente<\/li>\n
    4. aplikimi i ndryshimeve n\u00eb blockchain n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb gjendjes, p\u00ebrdit\u00ebsimi i t\u00eb dh\u00ebnave rreth transaksioneve dhe blloqeve<\/li>\n
    5. k\u00ebrkesa read-only n\u00eb baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb gjendjes, API e nodit blockchain, sh\u00ebrbimet e abonimit <\/li>\n<\/ol>\n

      <\/p>\n

      N\u00eb p\u00ebrgjith\u00ebsi, k\u00ebrkesat teknike p\u00ebr nodet e blockchain-eve moderne jan\u00eb jasht\u00ebzakonisht serioze - k\u00ebrkohen CPU t\u00eb shpejt\u00eb p\u00ebr kriptografin\u00eb, nj\u00eb sasi t\u00eb madhe kujtes\u00eb t\u00eb shpejt\u00eb p\u00ebr t\u00eb ruajtur dhe aksesuar shpejt baz\u00ebn e t\u00eb dh\u00ebnave t\u00eb gjendjes, nd\u00ebrveprimi n\u00eb rrjet q\u00eb p\u00ebrdor nj\u00eb num\u00ebr t\u00eb madh lidhjesh t\u00eb hapura nj\u00ebkoh\u00ebsisht, dhe hap\u00ebsir\u00eb t\u00eb madhe ruajtjeje. K\u00ebto k\u00ebrkesa t\u00eb larta dhe varieteti i llojeve t\u00eb operacioneve do t\u00eb sjellin domosdoshm\u00ebrish q\u00eb resurset e nodve t\u00eb mos mjaftojn\u00eb, dhe n\u00eb at\u00eb rast, \u00e7do nj\u00eb nga fazat e shqikuara m\u00eb sip\u00ebr mund t\u00eb b\u00ebhet nj\u00eb ngushtic\u00eb tjet\u00ebr p\u00ebr performanc\u00ebn e p\u00ebrgjithshme t\u00eb rrjetit.<\/p>\n

      <\/p>\n

      Kur zhvilloni dhe vler\u00ebsoni performanc\u00ebn e blockchain-eve, do t'ju duhet t\u00eb merrni parasysh t\u00eb gjitha k\u00ebto aspekte. P\u00ebr k\u00ebt\u00eb, nevojitet t\u00eb grumbulloni dhe analizoni metrikat n\u00eb m\u00ebnyr\u00eb t\u00eb p\u00ebrshtatshme nga klient\u00ebt dhe nod\u00ebt e rrjetit, t\u00eb k\u00ebrkoni korrelacione mes tyre, t\u00eb vler\u00ebsoni koh\u00ebn e ofrimit t\u00eb sh\u00ebrbimeve p\u00ebr klient\u00ebt, t\u00eb keni parasysh t\u00eb gjitha resurset kryesore: cpu\/memorie\/reti\/storage, t\u00eb kuptoni si p\u00ebrdoren dhe si ndikojn\u00eb nj\u00ebra me tjetr\u00ebn. T\u00eb gjitha k\u00ebto e b\u00ebjn\u00eb krahasimin e shpejt\u00ebsive t\u00eb blockchain-eve t\u00eb ndryshme n\u00eb form\u00ebn \"sa TPS\" jasht\u00ebzakonisht t\u00eb pak\u00ebndshme, sepse ekziston nj\u00eb num\u00ebr i madh konfiguracionesh dhe gjendjesh t\u00eb ndryshme. N\u00eb sisteme t\u00eb m\u00ebdha centralizuara, grupe me qindra server\u00eb, k\u00ebto probleme jan\u00eb gjithashtu t\u00eb komplikuara dhe k\u00ebrkojn\u00eb mbledhjen e nj\u00eb numri t\u00eb madh metrike t\u00eb ndryshme, por n\u00eb blockchain-e, p\u00ebr shkak t\u00eb rrjeteve p2p, makinave virtuele, kontratave t\u00eb prosesit, ekonomi t\u00eb brendshme, numri i niveleve t\u00eb liris\u00eb \u00ebsht\u00eb shum\u00eb m\u00eb i madh, duke e b\u00ebr\u00eb testimin edhe n\u00eb disa server\u00eb t\u00eb pambrojtur dhe duke treguar vet\u00ebm vlera t\u00eb pap\u00ebrcaktuara, pothuajse pa lidhje me realitetin.<\/p>\n

      <\/p>\n

      Prandaj, kur zhvillojm\u00eb n\u00eb thelb t\u00eb blockchain-it, p\u00ebr t\u00eb vler\u00ebsuar performanc\u00ebn dhe p\u00ebr t\u00eb p\u00ebrgjigjur pyetjes \"a \u00ebsht\u00eb p\u00ebrmir\u00ebsuar krahasuar me her\u00ebn e kaluar?\" ne p\u00ebrdorim nj\u00eb softuer t\u00eb quite t\u00eb komplikuar, i cili orkestron nisjen e blockchain-it me dhjet\u00ebra nod\u00eb dhe nisjen automatike t\u00eb benchmark-ut dhe grumbullimin e metrikave, pa k\u00ebt\u00eb informacion \u00ebsht\u00eb jasht\u00ebzakonisht e v\u00ebshtir\u00eb t\u00eb optimizosh protokollet q\u00eb funksionojn\u00eb me shum\u00eb pjes\u00ebmarr\u00ebs.<\/p>\n

      <\/p>\n

      K\u00ebshtu q\u00eb, kur merrni pyetjen \"sa TPS ka blockchain-i juaj?\", ofroni nj\u00eb filxhan \u00e7aj dhe sqaroni n\u00ebse ata jan\u00eb t\u00eb gatsh\u00ebm t\u00eb njohin nj\u00eb duzin\u00eb grafik\u00eb si dhe t\u00eb d\u00ebgjojn\u00eb t\u00eb gjitha problemet e performanc\u00ebs s\u00eb blockchain-eve dhe propozimet tuaja p\u00ebr zgjidhjen e tyre...<\/p>\n

      Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

      \u041b\u044e\u0431\u0438\u043c\u044b\u043c \u0432\u043e\u043f\u0440\u043e\u0441\u043e\u043c \u043e \u043b\u044e\u0431\u043e\u0439 \u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u0435 \u043e\u0442 \u043d\u0435\u0442\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u043e\u0433\u043e \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0441\u0442\u0430 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u201c\u0421\u043a\u043e\u043b\u044c\u043a\u043e tps \u0432 \u0432\u0430\u0448\u0435\u043c \u0431\u043b\u043e\u043a\u0447\u0435\u0439\u043d\u0435?\u201d. \u041e\u0434\u043d\u0430\u043a\u043e, \u043d\u0430\u0437\u0432\u0430\u043d\u043d\u043e\u0435 \u0432 \u043e\u0442\u0432\u0435\u0442 \u0447\u0438\u0441\u043b\u043e \u043e\u0431\u044b\u0447\u043d\u043e \u0438\u043c\u0435\u0435\u0442 \u043c\u0430\u043b\u043e \u043e\u0431\u0449\u0435\u0433\u043e \u0441 \u0442\u0435\u043c, \u0447\u0442\u043e \u0445\u043e\u0442\u0435\u043b \u0431\u044b \u0443\u0441\u043b\u044b\u0448\u0430\u0442\u044c \u0432\u043e\u043f\u0440\u043e\u0448\u0430\u044e\u0449\u0438\u0439. \u041d\u0430 \u0434\u0435\u043b\u0435, \u043e\u043d \u0445\u043e\u0442\u0435\u043b \u0441\u043f\u0440\u043e\u0441\u0438\u0442\u044c \u201c\u043f\u043e\u0434\u043e\u0439\u0434\u0435\u0442 \u043b\u0438 \u0432\u0430\u0448 \u0431\u043b\u043e\u043a\u0447\u0435\u0439\u043d \u043f\u043e\u0434 \u043c\u043e\u0438 \u0431\u0438\u0437\u043d\u0435\u0441 \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f\u201d, \u0438 \u044d\u0442\u0438 \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f \u2014 \u044d\u0442\u043e \u043d\u0435 \u043e\u0434\u043d\u043e \u0447\u0438\u0441\u043b\u043e, \u0430 \u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u043e \u0443\u0441\u043b\u043e\u0432\u0438\u0439 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-36157","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Sa TPS ka bllokada juaj? | ProHoster","description":"Pyetja e preferuar p\u00ebr \u00e7do sistem t\u00eb shp\u00ebrndar\u00eb nga nj\u00eb specialist jo teknik \u00ebsht\u00eb \"Sa tps ka bllokada juaj?\".","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/skolko-tps-v-vashem-blokchejne","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0421\u043a\u043e\u043b\u044c\u043a\u043e TPS \u0432 \u0432\u0430\u0448\u0435\u043c \u0431\u043b\u043e\u043a\u0447\u0435\u0439\u043d\u0435? | ProHoster","og:description":"\u041b\u044e\u0431\u0438\u043c\u044b\u043c \u0432\u043e\u043f\u0440\u043e\u0441\u043e\u043c \u043e \u043b\u044e\u0431\u043e\u0439 \u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u0435 \u043e\u0442 \u043d\u0435\u0442\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u043e\u0433\u043e \u0441\u043f\u0435\u0446\u0438\u0430\u043b\u0438\u0441\u0442\u0430 \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u201c\u0421\u043a\u043e\u043b\u044c\u043a\u043e tps \u0432 \u0432\u0430\u0448\u0435\u043c \u0431\u043b\u043e\u043a\u0447\u0435\u0439\u043d\u0435?\u201d.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/skolko-tps-v-vashem-blokchejne","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:09:55+00:00","article:modified_time":"2019-10-31T19:09:55+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"36157","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-22 02:15:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:49:44","updated":"2026-01-22 02:15:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/36157","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=36157"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/36157\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=36157"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=36157"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=36157"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}