{"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\/ro\/blog\/administrirovanie\/check-point-optimizatsiya-cpu-i-ram","title":{"rendered":"Check Point: optimizarea CPU \u0219i RAM","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Check
\nBun\u0103 ziua, colegi! Ast\u0103zi a\u0219 dori s\u0103 discut\u0103m despre un subiect foarte important pentru mul\u021bi administratori Check Point: \u201eOptimizarea CPU \u0219i RAM\u201d. Nu sunt rare cazurile \u00een care gateway-ul \u0219i\/sau serverul de management consum\u0103 o cantitate nea\u0219teptat\u0103 din aceste resurse, iar dorin\u021ba este s\u0103 \u00een\u021belegem unde \u201ese duc\u201d acestea \u0219i, dac\u0103 este posibil, s\u0103 le folosim mai eficient. <\/p>\n

1. Analiz\u0103<\/h3>\n

\nPentru analiza sarcinii procesorului, este util s\u0103 folosi\u021bi urm\u0103toarele comenzi, care sunt introduse \u00een modul expert:
\n<\/a><\/noindex>
\ntop<\/b> arat\u0103 toate procesele, cantitatea de resurse consumate de CPU \u0219i RAM \u00een procente, uptime, prioritatea procesului \u0219i altele<\/a><\/noindex> \u00een timp real<\/i>\u0219i <\/p>\n

\"Check
\n
\ncpwd_admin list<\/b> Check Point WatchDog Daemon, care arat\u0103 toate modulele appliance-ului, PID-ul lor, starea \u0219i num\u0103rul de porniri<\/i><\/p>\n

\"Check
\n
\ncpstat -f cpu os<\/b> utilizarea CPU, num\u0103rul acestora \u0219i distribuirea timpului procesorului \u00een procente<\/i><\/p>\n

\"Check
\n
\ncpstat -f memory os<\/b> utilizarea RAM-ului virtual, c\u00e2t\u0103 memorie activ\u0103 este disponibil\u0103, memorie liber\u0103 \u0219i altele<\/i><\/p>\n

\"Check
\n
\nO observa\u021bie corect\u0103 ar fi c\u0103 toate comenzile cpstat pot fi vizualizate cu ajutorul utilitarului cpview<\/b>. Pentru aceasta, trebuie doar s\u0103 introduce\u021bi comanda cpview din orice mod \u00eentr-o sesiune SSH.<\/p>\n

\"Check
\n\"Check
\n
\nps auxwf<\/b> o list\u0103 lung\u0103 a tuturor proceselor, ID-urile lor, memoria virtual\u0103 ocupat\u0103 \u0219i memoria din RAM, CPU<\/i><\/p>\n

\"Check
\n
\nO alt\u0103 varia\u021bie a comenzii: <\/p>\n

ps -aF<\/b> va ar\u0103ta cel mai costisitor proces<\/i><\/p>\n

\"Check
\n
\nfw ctl affinity -l -a<\/b> distribu\u021bia nucleelor pentru diferite instan\u021be ale firewall-ului, adic\u0103 tehnologia CoreXL<\/i><\/p>\n

\"Check
\n
\n fw ctl pstat<\/b> analiza RAM-ului \u0219i statisticile generale ale conexiunilor, cookies, NAT<\/i><\/p>\n

\"Check
\n
\nfree -m<\/b> buffer RAM<\/i><\/p>\n

\"Check
\n
\nO comand\u0103 care merit\u0103 men\u021bionat\u0103 este netsat <\/b>\u0219i varia\u021biile acesteia. De exemplu, netstat -i<\/b> poate ajuta la rezolvarea problemei monitoriz\u0103rii bufferelor de schimb. Parametrul RX dropped packets (RX-DRP) din ie\u0219irea acestei comenzi, \u00een general, cre\u0219te de la sine din cauza dropurilor de protocoale ilegitime (IPv6, etichete VLAN eronate\/neintenzionate \u0219i altele). Cu toate acestea, dac\u0103 dropurile apar dintr-un alt motiv, merit\u0103 s\u0103 folosi\u021bi aceast\u0103 articol<\/a><\/noindex>, pentru a \u00eencepe o investiga\u021bie \u0219i a \u00een\u021belege de ce aceast\u0103 interfa\u021b\u0103 de re\u021bea respinge pachetele. Odat\u0103 ce cauza este identificat\u0103, func\u021bionarea appliance-ului poate fi, de asemenea, optimizat\u0103.<\/p>\n

\"Check
\n
\nDac\u0103 blade-ul Monitoring este activat, este posibil s\u0103 vizualiza\u021bi aceste date grafic \u00een SmartConsole, ap\u0103s\u00e2nd pe obiect \u0219i select\u00e2nd \u201eDevice & License Information\u201d. <\/p>\n

Este recomandat s\u0103 nu activa\u021bi blade-ul Monitoring permanent, dar \u00eel pute\u021bi activa pentru o zi pentru teste.<\/p>\n

\"Check
\n
\n\u00cen plus, se pot ad\u0103uga mai multe parametrii pentru monitorizare, unul dintre ace\u0219tia fiind foarte util \u2014 Bytes Throughput (l\u0103\u021bimea de band\u0103 a appliance-ului).<\/p>\n

\"Check
\n
\nDac\u0103 exist\u0103 un alt sistem de monitorizare, de exemplu, un sistem gratuit Zabbix<\/a><\/noindex>, bazat pe SNMP, acesta se va potrivi pentru identificarea problemelor respective.<\/p>\n

2. \u201eScurgerea\u201d RAM \u00een timp<\/h3>\n

\nAdesea apare \u00eentrebarea de ce, \u00een timp, gateway-ul sau serverul de management \u00eencep s\u0103 consume tot mai mult RAM. Vreau s\u0103 te lini\u0219tesc: aceasta este o situa\u021bie normal\u0103 pentru sistemele asem\u0103n\u0103toare Linux. <\/p>\n

Privind ie\u0219irea comenzii free -m<\/b> \u0219i cpstat -f memory os<\/b> de pe appliance din modul expert, po\u021bi calcula \u0219i vizualiza to\u021bi parametrii referitori la RAM.<\/p>\n

De fapt, memoria disponibil\u0103 pe gateway \u00een acest moment Memorie liber\u0103<\/b> + Memorie buffer<\/b> + Memorie cache<\/b> = +-1.5 GB<\/b>, de obicei.<\/p>\n

A\u0219a cum spune SR, \u00een timp, gateway-ul\/serverul de management se optimizeaz\u0103 \u0219i folose\u0219te din ce \u00een ce mai mult\u0103 memorie, ajung\u00e2nd la aproximativ 80% utilizare, \u0219i se opre\u0219te. Po\u021bi s\u0103 reporne\u0219ti dispozitivul, iar atunci indicatorul se va reseta. 1.5 GB de RAM liber\u0103 este suficient pentru a \u00eendeplini toate sarcinile, iar serverul de management rar ajunge la astfel de valori limit\u0103.<\/p>\n

De asemenea, ie\u0219irile comenzilor men\u021bionate vor ar\u0103ta c\u00e2t de mult ai Memorie slab\u0103<\/b> (memorie operativ\u0103 \u00een user space) \u0219i Memorie \u00eenalt\u0103<\/b> (memorie operativ\u0103 \u00een kernel space) utilizat\u0103.<\/p>\n

Procesele kernel (inclusiv modulele active, cum ar fi modulele kernel Check Point) folosesc doar memorie slab\u0103. Cu toate acestea, procesele utilizatorului pot folosi at\u00e2t memorie slab\u0103, c\u00e2t \u0219i memorie \u00eenalt\u0103. Mai mult, memorie slab\u0103 este aproximativ egal\u0103 cu Memorie total\u0103<\/b>.<\/p>\n

Trebuie s\u0103 te \u00eengrijorezi doar dac\u0103 \u00een jurnale apar erori \u201emodule reboot sau procesele fiind \u00eenchise pentru a recupera memorie din cauza OOM (Out of memory)\u201d<\/b>. Atunci ar trebui s\u0103 reporne\u0219ti gateway-ul \u0219i s\u0103 contactezi suportul dac\u0103 repornirea nu ajut\u0103.<\/p>\n

O descriere complet\u0103 poate fi g\u0103sit\u0103 \u00een sk99547 <\/a><\/noindex>\u0219i sk99593<\/a><\/noindex>.<\/p>\n

3. Optimizare<\/h3>\n

\nMai jos sunt \u00eentreb\u0103ri \u0219i r\u0103spunsuri despre optimizarea CPU \u0219i RAM. Acestea merit\u0103 s\u0103 fie analizate serios \u0219i s\u0103 ascul\u021bi recomand\u0103rile.<\/p>\n

3.1. A fost selectat corect appliance-ul? A existat un proiect pilot?<\/h4>\n

\n\u00cen ciuda dimension\u0103rii corecte, re\u021beaua ar fi putut pur \u0219i simplu s\u0103 creasc\u0103, iar acest echipament s\u0103 nu fac\u0103 fa\u021b\u0103 sarcinii. A doua variant\u0103 este c\u0103 nu a existat o dimensionare efectiv\u0103.<\/p>\n

3.2. Este activat\u0103 inspec\u021bia HTTPS? Dac\u0103 da, este tehnologia configurat\u0103 conform celor mai bune practici? <\/h4>\n

\nContacteaz\u0103 articolul<\/a><\/noindex>, dac\u0103 e\u0219ti clientul nostru, sau sk108202<\/a><\/noindex>.<\/p>\n

Ordinea \u00een care sunt plasate regulile \u00een politica de inspec\u021bie HTTPS are o mare importan\u021b\u0103 \u00een optimizarea deschiderii site-urilor HTTPS.<\/p>\n

Ordinea recomandat\u0103 a plas\u0103rii regulilor:<\/p>\n

    \n
  1. Reguli bypass cu categorii\/URL<\/li>\n
  2. Reguli inspect cu categorii\/URL<\/li>\n
  3. Reguli inspect pentru toate celelalte categorii<\/li>\n<\/ol>\n

    \n\"Check
    \n
    \nAsemenea politicii de firewall, Check Point caut\u0103 potriviri \u00een pachete de sus \u00een jos, de aceea este mai bine s\u0103 plasa\u021bi regulile bypass \u00een partea de sus, deoarece gateway-ul nu va consuma resurse pentru a verifica toate regulile dac\u0103 acel pachet trebuie s\u0103 fie ocolit.<\/p>\n

    3.3 Sunt utilizate obiecte de tip address-range?<\/h4>\n

    \nObiectele cu un interval de adrese, de exemplu, re\u021beaua 192.168.0.0-192.168.5.0, consum\u0103 semnificativ mai mult RAM dec\u00e2t 5 obiecte de re\u021bea. \u00cen general, se consider\u0103 o bun\u0103 practic\u0103 s\u0103 elimina\u021bi obiectele neutilizate \u00een SmartConsole, deoarece de fiecare dat\u0103 c\u00e2nd este implementat\u0103 politica, gateway-ul \u0219i serverul de management consum\u0103 resurse \u0219i, mai ales, timp pentru a verifica \u0219i aplica politica.<\/p>\n

    3.4. Cum este configurat\u0103 politica de prevenire a amenin\u021b\u0103rilor? <\/h4>\n

    \n\u00cen primul r\u00e2nd, Check Point recomand\u0103 separarea IPS \u00eentr-un profil distinct \u0219i crearea de reguli separate pentru acest blade. <\/p>\n

    De exemplu, administratorul consider\u0103 c\u0103 segmentul DMZ trebuie protejat doar prin IPS. Astfel, pentru a nu consuma resursele gateway-ului pentru a procesa pachete cu alte blade-uri, este necesar s\u0103 crea\u021bi o regul\u0103 specific\u0103 pentru acest segment cu un profil \u00een care este activat doar IPS.<\/p>\n

    Referitor la configurarea profilurilor, este recomandabil s\u0103 fie configurate conform celor mai bune practici descrise \u00een acest document<\/a><\/noindex>(pagini 17-20).<\/p>\n

    3.5. \u00cen set\u0103rile IPS, c\u00e2te semn\u0103turi sunt \u00een modul Detect? <\/h4>\n

    \nSe recomand\u0103 s\u0103 se lucreze intens la semn\u0103turi, \u00een sensul c\u0103 ar trebui s\u0103 se dezactiveze cele neutilizate (de exemplu, semn\u0103turile legate de exploatarea produselor Adobe necesit\u0103 mult\u0103 putere computa\u021bional\u0103, iar dac\u0103 clientul nu are aceste produse, semn\u0103turile ar trebui dezactivate). Apoi, ar trebui s\u0103 se seteze Prevent \u00een loc de Detect acolo unde este posibil, deoarece gateway-ul consum\u0103 resurse pentru a procesa \u00eentreaga conexiune \u00een modul Detect, iar \u00een modul Prevent respinge imediat conexiunea \u0219i nu consum\u0103 resurse pentru o procesare complet\u0103 a pachetului.<\/p>\n

    3.6. Ce fi\u0219iere sunt procesate de blade-urile de Emulare a Amenin\u021b\u0103rilor, Extrac\u021bie de Amenin\u021b\u0103ri, Anti-Virus?<\/h4>\n

    \nNu are sens s\u0103 emula\u021bi \u0219i s\u0103 analiza\u021bi fi\u0219ierele de extensie pe care utilizatorii dvs. nu le descarc\u0103 sau pe care le considera\u021bi inutile \u00een re\u021beaua dvs. (de exemplu, fi\u0219ierele bat, exe pot fi u\u0219or blocate cu ajutorul blade-ului de Con\u0219tientizare a Con\u021binutului la nivelul firewall-ului, astfel \u00eenc\u00e2t resursele gateway-ului vor fi consumate mai pu\u021bin). \u00cen plus, \u00een set\u0103rile Emula\u021biei de Amenin\u021b\u0103ri, pute\u021bi alege Mediul (sistemul de operare) pentru emularea amenin\u021b\u0103rilor \u00een sandbox \u0219i alegerea Mediului Windows 7, c\u00e2nd to\u021bi utilizatorii lucreaz\u0103 cu versiunea 10, de asemenea, nu are sens.<\/p>\n

    3.7. Sunt regulile firewall-ului \u0219i regulile nivelului Aplicare plasate conform celor mai bune practici? <\/h4>\n

    \nDac\u0103 o regul\u0103 are multe hituri (corel\u0103ri), se recomand\u0103 s\u0103 fie plasat\u0103 \u00een partea de sus, iar regulile cu un num\u0103r redus de hituri s\u0103 fie plasate \u00een partea de jos. Principalul lucru este s\u0103 v\u0103 asigura\u021bi c\u0103 acestea nu se suprapun \u0219i nu se intersecteaz\u0103 \u00eentre ele. Arhitectura recomandat\u0103 a politicii de firewall este:<\/p>\n

    \"Check
    \n
    \nExplica\u021bii: <\/p>\n

    Reguli Ini\u021biale \u2014 aici se plaseaz\u0103 regulile cu cele mai multe corel\u0103ri
    \nRegula de Zgomot \u2014 regul\u0103 pentru a elimina traficul parazitar, cum ar fi NetBIOS
    \nRegula Stealth \u2014 interzicerea accesului la gateway-uri \u0219i gestion\u0103ri tuturor, cu excep\u021bia surselor specificate \u00een regulile de Autentificare la Regulile Gateway
    \nRegulile Clean-Up, Last \u0219i Drop sunt de obicei combinate \u00eentr-o singur\u0103 regul\u0103 pentru a interzice tot ce nu a fost anterior permis<\/p>\n

    Aceste date despre cele mai bune practici sunt descrise \u00een sk106597<\/a><\/noindex>.<\/p>\n

    3.8. Ce set\u0103ri au fost stabilite pentru serviciile create de administratori? <\/h4>\n

    \nDe exemplu, se creeaz\u0103 un anumit serviciu TCP pe un anumit port, \u0219i este de sens s\u0103 debifa\u021bi op\u021biunea \u201eMatch for Any\u201d \u00een set\u0103rile Avansate ale serviciului. \u00cen acest caz, acest serviciu va c\u0103dea specific sub regula \u00een care este men\u021bionat \u0219i nu va participa \u00een regulile unde \u00een coloana Servicii este specificat Any.<\/p>\n

    \"Check
    \n
    \nVorbind despre servicii, merit\u0103 men\u021bionat c\u0103 uneori este necesar s\u0103 ajusta\u021bi timpii de a\u0219teptare. Aceast\u0103 setare va permite o utilizare mai eficient\u0103 a resurselor gateway-ului, pentru a nu men\u021bine sesiuni TCP\/UDP inutile pentru protocoalele care nu necesit\u0103 un timp de a\u0219teptare mare. De exemplu, \u00een captura de ecran de mai jos, am modificat timpul de a\u0219teptare al serviciului domain-udp de la 40 de secunde la 30 de secunde.<\/p>\n

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

    3.9. Este utilizat SecureXL \u0219i care este procentajul de accelerare? <\/h4>\n

    \nCalitatea func\u021bion\u0103rii SecureXL poate fi verificat\u0103 cu comenzile principale \u00een modul expert pe gateway fwaccel stat<\/b> \u0219i fw accel stats -s<\/b>. Apoi, trebuie s\u0103 \u00een\u021belege\u021bi ce trafic este accelerat, ce \u0219abloane pot fi create suplimentar. <\/p>\n

    Implicit, \u0219abloanele Drop nu sunt activate, activarea lor va avea un impact negativ asupra func\u021bion\u0103rii SecureXL. Pentru aceasta, accesa\u021bi set\u0103rile gateway-ului \u0219i tab-ul Optimizations:<\/p>\n

    \"Check
    \n
    \nDe asemenea, atunci c\u00e2nd lucra\u021bi cu un cluster, pentru a optimiza CPU, pute\u021bi dezactiva sincronizarea serviciilor non-critice, cum ar fi UDP DNS, ICMP \u0219i altele. Pentru aceasta, este necesar s\u0103 accesa\u021bi set\u0103rile serviciului \u2192 Advanced \u2192 Synchronize connections of State Synchronization is enabled on the cluster.<\/p>\n

    \"Check
    \n
    \nToate cele mai bune practici sunt descrise \u00een     sk98348<\/a><\/noindex>.<\/p>\n

    3.10. Cum se utilizeaz\u0103 CoreXl? <\/h4>\n

    \nTehnologia CoreXL, care permite utilizarea mai multor CPU pentru instan\u021bele firewall (modulele firewall-ului), ajut\u0103 deosebit la optimizarea func\u021bion\u0103rii dispozitivului. Mai \u00eent\u00e2i, comanda fw ctl affinity -l -a <\/b>va ar\u0103ta instan\u021bele firewall utilizate \u0219i procesoarele alocate pentru necesitatea SND (modul care distribuie traficul c\u0103tre entit\u0103\u021bile firewall). Dac\u0103 nu toate procesoarele sunt utilizate, acestea pot fi ad\u0103ugate prin comanda cpconfig <\/b>pe gateway.
    \nDe asemenea, o poveste bun\u0103 este s\u0103 instala\u021bi     hotfixul <\/a><\/noindex>pentru activarea Multi-Queue. Multi-Queue rezolv\u0103 problema \u00een care procesorul cu SND este utilizat \u00eentr-un procent mare, \u00een timp ce instan\u021bele firewall-ului de pe celelalte procesoare sunt inactive. Prin urmare, SND ar avea posibilitatea de a crea multe cozi pentru un singur NIC \u0219i de a stabili diferite priorit\u0103\u021bi pentru diferit trafic la nivel de kernel. Astfel, nuclee CPU vor fi utilizate mai eficient. Metodologiile sunt de asemenea descrise \u00een sk98348<\/a><\/noindex>.<\/p>\n

    \u00cen concluzie, a\u0219 dori s\u0103 spun c\u0103 acestea nu sunt toate cele mai bune practici pentru optimizarea func\u021bion\u0103rii Check Point, ci doar cele mai populare. Dac\u0103 dori\u021bi s\u0103 solicita\u021bi un audit al politicii dumneavoastr\u0103 de securitate sau s\u0103 rezolva\u021bi o problem\u0103 legat\u0103 de Check Point, v\u0103 rug\u0103m s\u0103 contacta\u021bi sales@tssolution.ru. <\/p>\n

    V\u0103 mul\u021bumesc pentru aten\u021bie!
    \n
    Sursa:     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: optimizarea CPU \u0219i RAM | ProHoster","description":"Salut, colegi!","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/check-point-optimizatsiya-cpu-i-ram","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/39415","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=39415"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/39415\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/39416"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=39415"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=39415"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=39415"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}