Mun yi magana game da dabara a labarin, a cikin wannan muna gwada HTTPS, amma a cikin ƙarin yanayin yanayi. Don gwaji, mun sami takardar shaidar Let's Encrypt kuma mun kunna matsi na Brotli zuwa 11.
A wannan karon za mu yi ƙoƙarin sake haifar da yanayin tura sabar akan VDS ko azaman na'ura mai kama da na'ura akan mai watsa shiri tare da ma'aunin sarrafawa. Don wannan dalili, an saita iyaka a:
- 25% - Wanda yayi daidai da mitar ~ 1350 MHz
- 35% -1890MHz
- 41% - 2214 MHz
- 65% - 3510 MHz
An rage adadin haɗin lokaci ɗaya daga 500 zuwa 1, 3, 5, 7 da 9,
Sakamako:
Jinkiri:
An haɗa TTFB musamman azaman gwaji daban, saboda HTTPD Tools yana ƙirƙirar sabon mai amfani ga kowane buƙatun mutum. Wannan gwajin har yanzu ya rabu da gaskiyar, saboda har yanzu mai amfani zai danna shafuka biyu, kuma a zahiri TTFP zai taka muhimmiyar rawa.
Na farko, gabaɗaya buƙatun farko bayan farkon farkon na'urar kama-da-wane ta IIS tana ɗaukar matsakaicin 120 ms.
Duk buƙatun na gaba suna nuna TTFP na 1.5 ms. Apache da Nginx suna baya baya game da wannan. Da kaina, marubucin ya ɗauki wannan gwajin a matsayin mafi bayyanawa kuma zai zaɓi wanda ya yi nasara bisa ga shi kawai.
Sakamakon ba abin mamaki bane tunda IIS caches sun riga sun matsa abun ciki a tsaye kuma baya damfara shi duk lokacin da aka isa ga shi.
Lokacin kashe kowane abokin ciniki
Don kimanta aiki, gwaji tare da haɗin kai 1 ya wadatar.
Misali, IIS ta kammala gwajin masu amfani da 5000 a cikin dakika 40, wanda shine buƙatun 123 a sakan daya.
Hotunan da ke ƙasa suna nuna lokacin har sai an canza abun cikin rukunin gaba ɗaya. Wannan shine adadin buƙatun da aka kammala a cikin ƙayyadadden lokaci. A cikin yanayinmu, 80% na duk buƙatun an sarrafa su a cikin 8ms akan IIS kuma a cikin 4.5ms akan Apache da Nginx, kuma 8% na duk buƙatun akan Apache da Nginx an kammala su a cikin tazara har zuwa 98 milliseconds.
Lokacin da aka aiwatar da buƙatun 5000:
Lokacin da aka aiwatar da buƙatun 5000:
Idan kuna da injin kama-da-wane tare da CPU 3.5GHz da muryoyi 8, to zaɓi abin da kuke so. Duk sabar yanar gizo suna kama da juna a wannan gwaji. Za mu yi magana game da wace sabar gidan yanar gizo za mu zaɓa ga kowane mai masaukin baki a ƙasa.
Idan ya zo ga wani yanayi mai ma'ana, duk sabar yanar gizo suna tafiya kai da kai.
Input:
Hotunan jinkiri tare da adadin haɗin lokaci guda. Slow da ƙananan ya fi kyau. An cire kashi 2% na ƙarshe daga ginshiƙi saboda za su sa ba za a iya karanta su ba.
Yanzu bari mu yi la'akari da zabin inda uwar garken aka shirya a kan kama-da-wane Hosting. Bari mu ɗauki nau'i-nau'i 4 a 2.2 GHz da kuma guda ɗaya a 1.8 GHz.
Yadda ake sikelin
Idan kun taɓa ganin abin da halaye na halin yanzu-voltage na vacuum triodes, pentodes, da sauransu yayi kama, waɗannan jadawali zasu san ku. Wannan shine abin da muke ƙoƙarin kamawa - jikewa. Iyaka shine lokacin da komai nawa adadin da kuka jefa, haɓakar aikin ba zai zama sananne ba.
A baya can, duk ƙalubalen shine aiwatar da 98% na buƙatun tare da mafi ƙarancin latency don duk buƙatun, kiyaye lanƙwasa a matsayin lebur kamar yadda zai yiwu. Yanzu, ta hanyar gina wani lanƙwasa, za mu sami mafi kyawun wurin aiki ga kowane sabar.
Don yin wannan, bari mu ɗauki alamar Buƙatun da biyu (RPR). Horizontal shine mitar, a tsaye shine adadin buƙatun da aka sarrafa a sakan daya, layuka sune adadin muryoyi.
Yana nuna alaƙar yadda Nginx ke aiwatar da buƙatun ɗaya bayan ɗaya. Cores 8 sun fi kyau a wannan gwajin.
Wannan jadawali yana nuna a sarari yadda mafi kyawun (ba yawa) Nginx ke aiki akan cibiya guda ɗaya. Idan kana da Nginx, ya kamata ka yi la'akari da rage adadin maɗaukaki zuwa ɗaya idan kana ɗaukar nauyin kawai masu tsaye.
IIS, ko da yake yana da mafi ƙasƙanci TTFB bisa ga DevTools a cikin Chrome, yana sarrafa rasa zuwa duka Nginx da Apache a cikin mummunan yaki tare da gwajin danniya daga Apache Foundation.
Dukkan lanƙwan jadawali an sake yin su da ƙarfe.
Wani irin ƙarshe:
Ee, Apache yana aiki mafi muni akan muryoyin 1 da 8, amma yana aiki kaɗan kaɗan akan 4.
Ee, Nginx akan 8 cores suna aiwatar da buƙatun mafi kyau ɗaya bayan ɗaya, akan nau'ikan 1 da 4, kuma yana aiki mafi muni idan akwai haɗi da yawa.
Haka ne, IID ya fi fi son 4 ga masu aiki da yawa da kuma fice-jita da fifita cores guda 8 don suttura mai amfani da kaya. Daga ƙarshe, IIS ya ɗan yi sauri fiye da kowa akan nau'ikan 8 a ƙarƙashin babban nauyi, kodayake duk sabobin suna kan daidai.
Wannan ba kuskuren awo bane, kuskuren anan bai wuce +-1ms ba. a cikin jinkiri kuma bai wuce +- 2-3 buƙatun daƙiƙa don RPR ba.
Sakamakon inda 8 cores yayi muni ba abin mamaki ba ne, yawancin nau'i-nau'i da SMT / Hyperthreading suna lalata aiki sosai idan muna da lokacin lokaci wanda dole ne mu kammala dukkan bututun.
source: www.habr.com