{"id":39415,"date":"2019-10-31T22:32:08","date_gmt":"2019-10-31T19:32:08","guid":{"rendered":"https:\/\/prohoster.info\/blog\/check-point-optimizatsiya-cpu-i-ram\/"},"modified":"2019-10-31T22:32:08","modified_gmt":"2019-10-31T19:32:08","slug":"check-point-optimizatsiya-cpu-i-ram","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/check-point-optimizatsiya-cpu-i-ram","title":{"rendered":"Check Point: optimizimi i CPU dhe RAM","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Check
\nP\u00ebrsh\u00ebndetje, koleg\u00eb! Sot doja t\u00eb diskutonja mbi nj\u00eb tem\u00eb shum\u00eb aktuale p\u00ebr shum\u00eb administrator\u00eb t\u00eb Check Point, \"Optimizimi i CPU dhe RAM\". Nuk jan\u00eb t\u00eb pakta rastet kur gateway dhe\/ose serveri i menaxhimit konsumojn\u00eb papritur shum\u00eb nga k\u00ebto burime, dhe do t\u00eb donim t\u00eb kuptonim se ku po \"shk\u00eblqejn\u00eb\" dhe sa m\u00eb sakt\u00eb t\u00eb mundemi p\u00ebr t'i p\u00ebrdorur ato. <\/p>\n

1. Analiza<\/h3>\n

\nP\u00ebr analiz\u00ebn e ngarkes\u00ebs s\u00eb procesorit, \u00ebsht\u00eb e dobishme t\u00eb p\u00ebrdoren komandat e m\u00ebposhtme, t\u00eb cilat shkruhen n\u00eb modalitetin ekspert:
\n<\/a><\/noindex>
\ntop<\/b> tregon t\u00eb gjith\u00eb proceset, sasin\u00eb e burimeve t\u00eb konsumuar CPU dhe RAM n\u00eb p\u00ebrqindje, uptime, prioritetin e procesit dhe t\u00eb tjera<\/a><\/noindex> n\u00eb koh\u00eb reale<\/i>dhe <\/p>\n

\"Check
\n
\ncpwd_admin list<\/b> Check Point WatchDog Daemon, q\u00eb tregon t\u00eb gjith\u00eb modulat e aparatit, PID e tyre, gjendjen dhe numrin e nisjeve<\/i><\/p>\n

\"Check
\n
\ncpstat -f cpu os<\/b> p\u00ebrdorimi i CPU, numri i tyre dhe shp\u00ebrndarja e koh\u00ebs s\u00eb procesorit n\u00eb p\u00ebrqindje<\/i><\/p>\n

\"Check
\n
\ncpstat -f memory os<\/b> p\u00ebrdorimi i RAM virtual, sa gjithsej \u00ebsht\u00eb aktive, RAM e lir\u00eb dhe t\u00eb tjera<\/i><\/p>\n

\"Check
\n
\nNj\u00eb v\u00ebmendje e duhur do t\u00eb ishte se t\u00eb gjitha komandat cpstat mund t\u00eb shikohen p\u00ebrmes utilitarit cpview<\/b>. P\u00ebr k\u00ebt\u00eb thjesht duhet t\u00eb shkruani komand\u00ebn cpview nga \u00e7do modalitet n\u00eb sesionin SSH.<\/p>\n

\"Check
\n\"Check
\n
\nps auxwf<\/b> nj\u00eb list\u00eb e gjat\u00eb e t\u00eb gjitha proceseve, ID e tyre, memoria virtuale e p\u00ebrdorur dhe RAM, CPU<\/i><\/p>\n

\"Check
\n
\nNj\u00eb variacion tjet\u00ebr i komand\u00ebs: <\/p>\n

ps -aF<\/b> do t\u00eb tregoj\u00eb procesin m\u00eb t\u00eb konsumuesh\u00ebm<\/i><\/p>\n

\"Check
\n
\nfw ctl affinity -l -a<\/b> shp\u00ebrndarja e b\u00ebrthamave p\u00ebr instance t\u00eb ndryshme t\u00eb firewall-it, pra teknologjia CoreXL<\/i><\/p>\n

\"Check
\n
\n fw ctl pstat<\/b> analiza e RAM dhe treguesit e p\u00ebrgjithsh\u00ebm t\u00eb lidhjeve, cookies, NAT<\/i><\/p>\n

\"Check
\n
\nfree -m<\/b> memoria e tamponit RAM<\/i><\/p>\n

\"Check
\n
\nNj\u00eb v\u00ebmendje t\u00eb ve\u00e7ant\u00eb meriton komand\u00ebn netsat <\/b>dhe variacionet e saj. P\u00ebr shembull, netstat -i<\/b> mund t\u00eb ndihmoj\u00eb p\u00ebr t\u00eb zgjidhur detyr\u00ebn e monitorimit t\u00eb tampon\u00ebve t\u00eb shk\u00ebmbimit. Parametri, RX dropped packets (RX-DRP) n\u00eb daljen e k\u00ebsaj komande, zakonisht rritet vet\u00eb p\u00ebr shkak t\u00eb hedhjeve t\u00eb protokolleve t\u00eb paligjshme (IPv6, Bad \/ Unintended VLAN tags dhe t\u00eb tjera). Megjithat\u00eb, n\u00ebse hedhjet ndodhin p\u00ebr nj\u00eb shkak tjet\u00ebr, at\u00ebher\u00eb \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb p\u00ebrdorim k\u00ebt\u00eb artikull<\/a><\/noindex>, p\u00ebr t\u00eb filluar hetimin dhe p\u00ebr t\u00eb kuptuar se p\u00ebrse ky nd\u00ebrfaqe rrjeti hedh paketa. Pasi t\u00eb dihet shkaku, puna e aparatit gjithashtu mund t\u00eb optimizohet.<\/p>\n

\"Check
\n
\nN\u00ebse blada e Monitoring \u00ebsht\u00eb e aktivizuar, at\u00ebher\u00eb mund t\u00eb shikoni k\u00ebto tregues grafikisht n\u00eb SmartConsole, duke klikuar n\u00eb objektin dhe duke zgjedhur opsionin \"Device & License Information\". <\/p>\n

Nuk rekomandohet aktivizimi i p\u00ebrhersh\u00ebm i bladas Monitoring, por \u00ebsht\u00eb plot\u00ebsisht i pranuesh\u00ebm p\u00ebr nj\u00eb dit\u00eb p\u00ebr testim.<\/p>\n

\"Check
\n
\nP\u00ebr m\u00eb tep\u00ebr, mund t\u00eb shtoni m\u00eb shum\u00eb parametra p\u00ebr monitorim, nj\u00eb prej t\u00eb cil\u00ebve \u00ebsht\u00eb shum\u00eb i dobish\u00ebm \u2014 Bytes Throughput (kapaciteti i pajisjes).<\/p>\n

\"Check
\n
\nN\u00ebse ka ndonj\u00eb sistem tjet\u00ebr monitorimi, p\u00ebr shembull, falas Zabbix<\/a><\/noindex>, i bazuar n\u00eb SNMP, ai gjithashtu do t\u00eb jet\u00eb i p\u00ebrshtatsh\u00ebm p\u00ebr identifikimin e k\u00ebtyre problemeve.<\/p>\n

2. \"Shkarkimi\" i RAM me kalimin e koh\u00ebs<\/h3>\n

\nShpesh lind pyetja se si me kalimin e koh\u00ebs gateway ose menaxhmenti i serverit fillon t\u00eb konsumoj\u00eb gjithnj\u00eb e m\u00eb shum\u00eb RAM. Dua t'ju qet\u00ebsoj: kjo \u00ebsht\u00eb nj\u00eb situat\u00eb normale p\u00ebr sistemet e ngjashme me Linux. <\/p>\n

Duke par\u00eb daljen e komandave free -m<\/b> dhe cpstat -f memory os<\/b> n\u00eb pajisje nga moda ekspert, mund t\u00eb llogarisni dhe t\u00eb shihni t\u00eb gjitha parametrat q\u00eb lidhen me RAM.<\/p>\n

N\u00eb fakt, memoria e disponueshme n\u00eb gateway aktualisht Memoria e Lir\u00eb<\/b> + Memoria e Bufrareve<\/b> + Memoria e Ruajtur<\/b> = +-1.5 GB<\/b>, si zakonisht.<\/p>\n

Si\u00e7 thot\u00eb SR, me kalimin e koh\u00ebs gateway\/serveri i menaxhimit optimizohet dhe p\u00ebrdor gjithnj\u00eb e m\u00eb shum\u00eb memorie, duke arritur deri n\u00eb rreth 80% t\u00eb p\u00ebrdorimit, dhe ndalon. Ju mund t\u00eb rindizni pajisjen, dhe at\u00ebher\u00eb m\u00eb treguesi do t\u00eb rikthehet. 1.5 GB RAM t\u00eb lir\u00eb i mjafton gateway p\u00ebr t\u00eb p\u00ebrmbushur t\u00eb gjitha detyrat, dhe menaxhmenti rrall\u00eb arrin n\u00eb k\u00ebto kufij.<\/p>\n

P\u00ebr m\u00eb tep\u00ebr, daljet e komandave t\u00eb p\u00ebrmendura do t\u00eb tregojn\u00eb se sa keni Memoria e Ul\u00ebt<\/b> (memoria operative n\u00eb user space) dhe Memoria e Lart\u00eb<\/b> (memoria operative n\u00eb kernel space) e p\u00ebrdorur.<\/p>\n

Proceset e kernelit (p\u00ebrfshir\u00eb modulet aktive, t\u00eb tilla si modulet e kernelit t\u00eb Check Point) p\u00ebrdorin vet\u00ebm Memori t\u00eb Ul\u00ebt. Megjithat\u00eb, proceset e p\u00ebrdoruesve mund t\u00eb p\u00ebrdorin si Memori t\u00eb Ul\u00ebt ashtu edhe t\u00eb Lart\u00eb. P\u00ebr m\u00eb tep\u00ebr, Memoria e Ul\u00ebt \u00ebsht\u00eb af\u00ebrsisht e barasvler\u00eb Memoria Totale<\/b>.<\/p>\n

Duhet t\u00eb shqet\u00ebsoheni vet\u00ebm n\u00ebse n\u00eb log-et bien gabime \"modules reboot or processes being killed to reclaim memory due to OOM (Out of memory)\"<\/b>. At\u00ebher\u00eb duhet t\u00eb rindizni gateway-in dhe t\u00eb kontaktoni mb\u00ebshtetjen n\u00ebse rindizja nuk ndihmon.<\/p>\n

P\u00ebrshkrimi i plot\u00eb mund t\u00eb gjendet n\u00eb sk99547 <\/a><\/noindex>dhe sk99593<\/a><\/noindex>.<\/p>\n

3. Optimizimi<\/h3>\n

\nM\u00eb posht\u00eb jan\u00eb pyetje dhe p\u00ebrgjigje n\u00eb lidhje me optimizimin e CPU dhe RAM. \u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb p\u00ebrgjigjeni sinqerisht vet\u00eb dhe t\u00eb d\u00ebgjoni rekomandimet.<\/p>\n

3.1. A ishte pajisja e zgjedhur si\u00e7 duhej? A kishte nj\u00eb projekt pilot?<\/h4>\n

\nPavar\u00ebsisht nga dimensionimi i sakt\u00eb, rrjeti mund t\u00eb jet\u00eb thjesht rritur, dhe kjo pajisje mbase nuk po p\u00ebrballon ngarkes\u00ebn. Nj\u00eb opsion tjet\u00ebr \u00ebsht\u00eb se nuk ka pasur dimensionim t\u00eb till\u00eb.<\/p>\n

3.2. A \u00ebsht\u00eb aktivizuar inspektimi HTTPS? N\u00ebse po, a \u00ebsht\u00eb konfiguruar teknologjia sipas Praktikave m\u00eb t\u00eb Mira? <\/h4>\n

\nKontaktoni artikulli<\/a><\/noindex>, n\u00ebse jeni klient yn\u00eb, ose n\u00eb sk108202<\/a><\/noindex>.<\/p>\n

Renditja e rregullave n\u00eb politik\u00ebn e inspektimit HTTPS ka nj\u00eb r\u00ebnd\u00ebsi t\u00eb madhe n\u00eb optimizimin e hapjes s\u00eb faqeve HTTPS.<\/p>\n

Renditja e rekomanduar e rregullave:<\/p>\n

    \n
  1. Rregullat bypass me kategori\/URL<\/li>\n
  2. Rregullat inspect me kategori\/URL<\/li>\n
  3. Rregullat inspect p\u00ebr t\u00eb gjitha kategorit\u00eb e tjera<\/li>\n<\/ol>\n

    \n\"Check
    \n
    \nP\u00ebr t\u00eb nj\u00ebjt\u00ebn arsye si politika e firewall-it, Check Point k\u00ebrkon p\u00ebrputhshm\u00ebri me paketat nga lart posht\u00eb, prandaj rregullat bypass duhet t\u00eb jen\u00eb pozicionuar lart, p\u00ebr shkak se gateway nuk do t\u00eb harxhoj\u00eb burime p\u00ebr t\u00eb kaluar p\u00ebrmes t\u00eb gjitha rregullave, n\u00ebse kjo paket\u00eb duhet t\u00eb lihet anash.<\/p>\n

    3.3 A p\u00ebrdoren objektet me range adresash?<\/h4>\n

    \nObjektet me range adresash, p\u00ebr shembull, rrjeti 192.168.0.0-192.168.5.0, konsumojn\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb konsiderueshme m\u00eb shum\u00eb RAM se sa 5 objekte rrjeti. N\u00eb p\u00ebrgjith\u00ebsi, praktika m\u00eb e mir\u00eb \u00ebsht\u00eb t\u00eb fshihni objektet e pap\u00ebrdorura n\u00eb SmartConsole, pasi \u00e7do her\u00eb gjat\u00eb vendosjes s\u00eb politik\u00ebs, gateway dhe serveri i menaxhimit harxhojn\u00eb burime dhe, m\u00eb e r\u00ebnd\u00ebsishmja, koh\u00eb, p\u00ebr t\u00eb verifikuar dhe zbatuar politik\u00ebn.<\/p>\n

    3.4 Si \u00ebsht\u00eb e konfiguruar politika e Parandalimit t\u00eb K\u00ebrc\u00ebnimeve? <\/h4>\n

    \nS\u00eb pari, Check Point rekomandon q\u00eb IPS t\u00eb vendoset n\u00eb nj\u00eb profil t\u00eb ve\u00e7ant\u00eb dhe q\u00eb t\u00eb krijohen rregulla t\u00eb ve\u00e7anta p\u00ebr k\u00ebt\u00eb blade. <\/p>\n

    P\u00ebr shembull, administratori konsideron se segmenti DMZ duhet t\u00eb mbrohet vet\u00ebm me an\u00eb t\u00eb IPS. Prandaj, p\u00ebr t\u00eb evituar q\u00eb gateway t\u00eb harxhoj\u00eb burime n\u00eb trajtimin e paketave nga blades t\u00eb tjera, \u00ebsht\u00eb e nevojshme t\u00eb krijohet nj\u00eb rregull specifik p\u00ebr k\u00ebt\u00eb segment me nj\u00eb profil q\u00eb p\u00ebrfshin vet\u00ebm IPS.<\/p>\n

    Sa i p\u00ebrket konfigurimit t\u00eb profileve, rekomandohet t\u00eb konfigurohet sipas praktika m\u00eb t\u00eb mira n\u00eb k\u00ebt\u00eb dokument<\/a><\/noindex>(faqet 17-20).<\/p>\n

    3.5 N\u00eb cil\u00ebsimet e IPS, sa shum\u00eb n\u00ebnshkrime jan\u00eb n\u00eb m\u00ebnyr\u00ebn Detect? <\/h4>\n

    \nRekomandohet q\u00eb t\u00eb punoni fort n\u00eb n\u00ebnshkrime n\u00eb at\u00eb aspekt q\u00eb duhet t\u00eb \u00e7aktivizoni ato t\u00eb pap\u00ebrdorura (p\u00ebr shembull, n\u00ebnshkrimet p\u00ebr shfryt\u00ebzimin e produkteve Adobe k\u00ebrkojn\u00eb shum\u00eb fuqi llogarit\u00ebse, dhe n\u00ebse klienti nuk ka k\u00ebto produkte, ka kuptim t\u00eb \u00e7aktivizoni n\u00ebnshkrimet). M\u00eb pas, vendosni Prevent n\u00eb vend t\u00eb Detect ku \u00ebsht\u00eb e mundur, sepse gateway harxhon burime p\u00ebr trajtimin e t\u00eb gjith\u00eb lidhjes n\u00eb m\u00ebnyr\u00ebn Detect, nd\u00ebrsa n\u00eb m\u00ebnyr\u00ebn Prevent ai menj\u00ebher\u00eb ibraktis lidhjen dhe nuk harxhon burime p\u00ebr trajtimin e plot\u00eb t\u00eb paket\u00ebs.<\/p>\n

    3.6 Cilat skedar\u00eb p\u00ebrpunohen nga blades t\u00eb Emulimit t\u00eb K\u00ebrc\u00ebnimeve, Ekstrakt\u00ebs s\u00eb K\u00ebrc\u00ebnimeve, Anti-Virus?<\/h4>\n

    \nNuk e ka kuptim t\u00eb emulosh dhe analizosh skedar\u00eb me zgjerime q\u00eb p\u00ebrdoruesit tuaj nuk i shkarkojn\u00eb, ose q\u00eb i konsideroni t\u00eb panevojsh\u00ebm n\u00eb rrjetin tuaj (p\u00ebr shembull, skedar\u00ebt bat, exe mund t\u00eb bllokohen leht\u00ebsisht me blade Content Awareness n\u00eb nivelin e firewall-it, k\u00ebshtu q\u00eb burimet e portalit do t\u00eb shpenzohen m\u00eb pak). P\u00ebr m\u00eb tep\u00ebr, n\u00eb cil\u00ebsimet e Emulimit t\u00eb K\u00ebrc\u00ebnimeve, mund t\u00eb zgjidhni Ambientin (sistemin operativ) p\u00ebr emulimin e k\u00ebrc\u00ebnimeve n\u00eb sandbox dhe t\u00eb vendosni Ambient Windows 7, nd\u00ebrsa t\u00eb gjith\u00eb p\u00ebrdoruesit punojn\u00eb me versionin 10, gjithashtu nuk ka kuptim.<\/p>\n

    3.7. A jan\u00eb t\u00eb vendosura rregullat e firewall-it dhe rregullat n\u00eb nivelin e Application sipas best practice? <\/h4>\n

    \nN\u00ebse nj\u00eb rregull ka shum\u00eb goditje (p\u00ebrputhje), at\u00ebher\u00eb rekomandohet q\u00eb ato t\u00eb vendosen n\u00eb krye, nd\u00ebrsa rregullat me num\u00ebr t\u00eb vog\u00ebl goditjesh t\u00eb vendosen n\u00eb fund. E r\u00ebnd\u00ebsishme \u00ebsht\u00eb q\u00eb t\u00eb siguroheni q\u00eb ato t\u00eb mos mbivendosen dhe t\u00eb mos mbulojn\u00eb nj\u00ebra-tjetr\u00ebn. Arkitektura e rekomanduar e politik\u00ebs s\u00eb firewall-it:<\/p>\n

    \"Check
    \n
    \nShpjegime: <\/p>\n

    Rregullat e Para \u2014 k\u00ebtu vendosen rregullat me numrin m\u00eb t\u00eb madh t\u00eb p\u00ebrputhjeve.
    \nRregulli i Zhurm\u00ebs \u2014 rregull p\u00ebr eliminimin e trafikut parazit, si NetBIOS.
    \nRregulli Stealth \u2014 ndalimi i t\u00eb gjitha k\u00ebrkesave p\u00ebr portat dhe menaxhimin p\u00ebrve\u00e7 k\u00ebtyre burimeve q\u00eb jan\u00eb treguar n\u00eb rregullat e Autentikimit p\u00ebr Rregullat e Port\u00ebs.
    \nRregullat e Pastrimit, t\u00eb Fundit dhe t\u00eb R\u00ebnies, zakonisht, bashkohen n\u00eb nj\u00eb rregull p\u00ebr t\u00eb ndaluar gjith\u00e7ka q\u00eb nuk \u00ebsht\u00eb lejuar m\u00eb par\u00eb.<\/p>\n

    T\u00eb dh\u00ebnat e Best practice jan\u00eb p\u00ebrshkruar n\u00eb sk106597<\/a><\/noindex>.<\/p>\n

    3.8. \u00c7far\u00eb cil\u00ebsimesh kan\u00eb sh\u00ebrbimet e krijuara nga administrator\u00ebt? <\/h4>\n

    \nP\u00ebr shembull, krijohet nj\u00eb sh\u00ebrbim TCP n\u00eb nj\u00eb port t\u00eb caktuar, dhe ka kuptim n\u00eb cil\u00ebsimet e Avancuara t\u00eb sh\u00ebrbimit q\u00eb t\u00eb hiqet shenja \"Match for Any\". N\u00eb k\u00ebt\u00eb rast, ky sh\u00ebrbim do t\u00eb p\u00ebrputhet konkretisht me rregullin ku figuron, dhe nuk do t\u00eb marr\u00eb pjes\u00eb n\u00eb rregullat ku n\u00eb kolon\u00ebn Sh\u00ebrbime \u00ebsht\u00eb Any.<\/p>\n

    \"Check
    \n
    \nDuke folur p\u00ebr sh\u00ebrbimet, ia vlen t\u00eb p\u00ebrmendim se ndonj\u00ebher\u00eb \u00ebsht\u00eb e nevojshme t\u00eb rregullosh timeout-et. Kjo cil\u00ebsim do t\u00eb lejoj\u00eb nj\u00eb shpenzim m\u00eb t\u00eb men\u00e7ur t\u00eb burimeve t\u00eb port\u00ebs, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb mos mbaj\u00eb p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb seancat e protokolleve TCP\/UDP q\u00eb nuk kan\u00eb nevoj\u00eb p\u00ebr nj\u00eb timeout t\u00eb madh. P\u00ebr shembull, n\u00eb screenshotin m\u00eb posht\u00eb, kam ndryshuar timeout-in e sh\u00ebrbimit domain-udp nga 40 sekonda n\u00eb 30 sekonda.<\/p>\n

    \"Check
    \n<\/p>\n

    3.9. A p\u00ebrdoret SecureXL dhe cila \u00ebsht\u00eb p\u00ebrqindja e p\u00ebrshpejtimit? <\/h4>\n

    \nShtoni cil\u00ebsin\u00eb e pun\u00ebs s\u00eb SecureXL \u00ebsht\u00eb e mundur me komandat kryesore n\u00eb modin ekspert n\u00eb portal. fwaccel stat<\/b> dhe fw accel stats -s<\/b>. M\u00eb pas duhet t\u00eb shqyrtohet cili trafik p\u00ebrshpejtohet, cilat templates (shabllone) mund t\u00eb krijohen m\u00eb shum\u00eb. <\/p>\n

    P\u00ebr default, Drop Templates nuk jan\u00eb t\u00eb aktivizuara, aktivizimi i tyre do t\u00eb ndikoj\u00eb pozitivisht n\u00eb funksionimin e SecureXL. P\u00ebr k\u00ebt\u00eb, hyni n\u00eb cil\u00ebsimet e port\u00ebs dhe n\u00eb sked\u00ebn Optimizimet:<\/p>\n

    \"Check
    \n
    \nGjithashtu, gjat\u00eb pun\u00ebs me klasterin, p\u00ebr t\u00eb optimizuar CPU-n\u00eb, mund t\u00eb \u00e7aktivizoni sinkronizimin e sh\u00ebrbimeve jo kritike, si UDP DNS, ICMP dhe t\u00eb tjera. P\u00ebr k\u00ebt\u00eb, shkoni n\u00eb cil\u00ebsimet e sh\u00ebrbimit \u2192 Avancuar \u2192 Sinkronizoni lidhjet kur Sinkronizimi i Shtetit \u00ebsht\u00eb aktivizuar n\u00eb klaster.<\/p>\n

    \"Check
    \n
    \nT\u00eb gjitha Praktikat m\u00eb t\u00eb Mira jan\u00eb t\u00eb p\u00ebrshkruara n\u00eb     sk98348<\/a><\/noindex>.<\/p>\n

    3.10. Si p\u00ebrdoret CoreXl? <\/h4>\n

    \nTeknologjia CoreXL, e cila lejon p\u00ebrdorimin e shum\u00eb CPU-ve p\u00ebr instancat e firewall-it, ndihmon pa dyshim n\u00eb optimizimin e funksionimit t\u00eb pajisjes. Fillimisht komanda fw ctl affinity -l -a <\/b>do t\u00eb tregoj\u00eb instancat e p\u00ebrdorura t\u00eb firewall-it dhe procesor\u00ebt e dh\u00ebn\u00eb p\u00ebr nevojat e SND (moduli q\u00eb shp\u00ebrndan trafik n\u00eb entitetet e firewall-it). N\u00ebse nuk jan\u00eb angazhuar t\u00eb gjitha procesor\u00ebt, mund t'i shtoni me komand\u00ebn cpconfig <\/b>n\u00eb port\u00eb.
    \nGjithashtu, nj\u00eb hap i mir\u00eb \u00ebsht\u00eb t\u00eb vendosni     patch-in <\/a><\/noindex>p\u00ebr aktivizimin e Multi-Queue. Multi-Queue zgjidh problemin kur procesori me SND p\u00ebrdoret n\u00eb shum\u00eb p\u00ebrqindje, nd\u00ebrsa instancat e firewall-it n\u00eb procesor\u00eb t\u00eb tjer\u00eb mbeten pa p\u00ebrdorim. K\u00ebshtu, SND do t\u00eb kishte mund\u00ebsin\u00eb t\u00eb krijonte shum\u00eb radh\u00eb p\u00ebr nj\u00eb NIC dhe t\u00eb vendoste prioritete t\u00eb ndryshme p\u00ebr trafik t\u00eb ndrysh\u00ebm n\u00eb nivelin e b\u00ebrtham\u00ebs. Si rezultat, b\u00ebrthamat e CPU-s\u00eb do t\u00eb p\u00ebrdoren m\u00eb sakt\u00eb. Metodikat jan\u00eb gjithashtu t\u00eb p\u00ebrshkruara n\u00eb sk98348<\/a><\/noindex>.<\/p>\n

    N\u00eb p\u00ebrfundim, do t\u00eb doja t\u00eb theksoja se nuk jan\u00eb t\u00eb gjitha Praktikat m\u00eb t\u00eb Mira p\u00ebr optimizimin e funksionimit t\u00eb Check Point, por jan\u00eb m\u00eb t\u00eb popullarizuarat. N\u00ebse d\u00ebshironi t\u00eb k\u00ebrkoni nj\u00eb audit t\u00eb politik\u00ebs suaj t\u00eb siguris\u00eb ose t\u00eb zgjidhni nj\u00eb problem q\u00eb lidhet me Check Point, ju lutem kontaktoni n\u00eb sales@tssolution.ru. <\/p>\n

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

    \u0417\u0434\u0440\u0430\u0432\u0441\u0442\u0432\u0443\u0439\u0442\u0435, \u043a\u043e\u043b\u043b\u0435\u0433\u0438! \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u044f \u0445\u043e\u0442\u0435\u043b \u0431\u044b \u043e\u0431\u0441\u0443\u0434\u0438\u0442\u044c \u043e\u0447\u0435\u043d\u044c \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u0443\u044e \u0434\u043b\u044f \u043c\u043d\u043e\u0433\u0438\u0445 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u043e\u0432 Check Point \u0442\u0435\u043c\u0443 \u00ab\u041e\u043f\u0442\u0438\u043c\u0438\u0437\u0430\u0446\u0438\u044f CPU \u0438 RAM\u00bb. \u041d\u0435\u0440\u0435\u0434\u043a\u0438 \u0441\u043b\u0443\u0447\u0430\u0438, \u043a\u043e\u0433\u0434\u0430 \u0448\u043b\u044e\u0437 \u0438\/\u0438\u043b\u0438 \u043c\u0435\u043d\u0435\u0434\u0436\u043c\u0435\u043d\u0442 \u0441\u0435\u0440\u0432\u0435\u0440 \u043f\u043e\u0442\u0440\u0435\u0431\u043b\u044f\u044e\u0442 \u043d\u0435\u043e\u0436\u0438\u0434\u0430\u043d\u043d\u043e \u043c\u043d\u043e\u0433\u043e \u044d\u0442\u0438\u0445 \u0440\u0435\u0441\u0443\u0440\u0441\u043e\u0432, \u0438 \u0445\u043e\u0442\u0435\u043b\u043e\u0441\u044c \u0431\u044b \u043f\u043e\u043d\u044f\u0442\u044c, \u043a\u0443\u0434\u0430 \u043e\u043d\u0438 \u201c\u0443\u0442\u0435\u043a\u0430\u044e\u0442\u201d, \u0438 \u043f\u043e \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0438 \u0433\u0440\u0430\u043c\u043e\u0442\u043d\u0435\u0435 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0438\u0445. 1. \u0410\u043d\u0430\u043b\u0438\u0437 \u0414\u043b\u044f \u0430\u043d\u0430\u043b\u0438\u0437\u0430 \u0437\u0430\u0433\u0440\u0443\u0437\u043a\u0438 \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u043e\u0440\u0430 \u043f\u043e\u043b\u0435\u0437\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u0435 \u043a\u043e\u043c\u0430\u043d\u0434\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":39416,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-39415","post","type-post","status-publish","format-standard","has-post-thumbnail","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\udd47Check Point: optimizimi i CPU-s\u00eb dhe RAM-it | ProHoster","description":"P\u00ebrsh\u00ebndetje, koleg\u00eb!","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/check-point-optimizatsiya-cpu-i-ram","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\udd47Check Point: \u043e\u043f\u0442\u0438\u043c\u0438\u0437\u0430\u0446\u0438\u044f CPU \u0438 RAM | ProHoster","og:description":"\u0417\u0434\u0440\u0430\u0432\u0441\u0442\u0432\u0443\u0439\u0442\u0435, \u043a\u043e\u043b\u043b\u0435\u0433\u0438!","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/check-point-optimizatsiya-cpu-i-ram","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:32:08+00:00","article:modified_time":"2019-10-31T19:32:08+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"39415","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-24 01:55:21","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 00:50:24","updated":"2026-01-24 01:55:21","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\/39415","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=39415"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/39415\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/39416"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=39415"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=39415"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=39415"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}