Caching & speed

Cache mai fadi da gado wanda ke kiyaye shafuka cikin sauri a babban sikelin

Yawancin ziyartce-ziyartce zuwa wani shafin Zinn Digital® ba sa taba PHP ko MySQL. Wurin ajiyar shafi na LiteSpeed, wurin ajiyar abu na Redis na kowane shafi, da kuma CDN edge suna aiki tare, ta hanyar wani tsari mai wayo na sharewa ta atomatik, ta yadda shafuka za su kasance cikin sauri kuma asali ya kasance cikin nutsuwa — a duk fadin shafuka sama da 650,000 da ake daukar nauyinsu a duniya.

Fara kyauta Duba farashi

Matakai uku na babban ajiyar wucin gadi, tsari guda da ke aiki tare

Sauri yana zuwa ne daga gabatar da abu mai kyau daga wuri mafi sauri. Mun haɗa caches guda uku ta yadda za a amsa buƙata da wuri sosai — a gefe (edge), a sabar gidan yanar gizo, ko daga ƙwaƙwalwa — kuma ba ta taɓa buƙatar sake gina shafin da ta riga ta gina ba.

LSCache cikakken ajiyar shafi

A kan masaukin LiteSpeed, ana sanya wa amsoshin gaba masu shiga ma'ajiya alamomin sarrafa ma'ajiya da na tag na LiteSpeed, ta yadda sabar gizo ke ba da shafuka cikakke ba tare da kiran PHP ko binciken MySQL ba. Wannan ita ce babbar nasara ta musamman ga lokacin zuwa amsa ta farko a kan WordPress.

Maajiyar abubuwa ta Redis ta kowane shafi

Acan sauƙi ta amfani da maballin dannawa ɗaya kawai, za ka iya shigar da drop-in na Redis object-cache wanda ke cin gashin kansa, wanda ke rage nauyin karatun database na akai-akai. Idan har aka samu matsalar samun Redis, drop-in ɗin yana komawa zuwa in-memory cache na kowace buƙata (per-request), ta yadda shafin zai ci gaba da aiki.

CDN da kuma gefe

Ana ba da kadarori marasa canzawa da shafukan da za a iya adanawa daga CDN kusa da masu ziyara. Ana tura goge-goge zuwa edge domin ya ci gaba da tafiya kafada da kafada da ma'ajiya ta asali — iko guda ɗaya, ba saaituwa uku a rarrabe ba.

Smart auto-purge yana kiyaye abubuwa cikin sabon hali

Ana amfani da cache ne kawai idan ya share shafukan da suka dace a daidaitaccen lokaci. Namu yana sanya idanu kaniniya-hali-na-gaske kuma yana sharewa da kyau ta amfani da alamomin LiteSpeed cache — ba wai kawai ya share komai ba a duk lokacin da aka yi gyara.

Lokacin da aka adana, aka sanya a cikin kwando, ko aka goge wani rubutu ko shafi, shafukan da abin ya shafa da jerin abubuwan da suke bayyana kawai ake sharewa.
Sharhi, shafuka da aka gyara, canjin jigo, kunna matosai da sabunta jigo ko tsarin tushe duk suna jawo hankalin tsaftacewa da aka yi niyya.
Yana share madubi zuwa ga panel na control-plane ta hanyar wani signed webhook, ta yadda CDN da edge za su yi share tare da asalin (origin).
Wani wurin sharewa na REST yana ba da damar kwamitin ya share komai, takamaiman URL-loli, ko takamaiman alamomi — wanda zaman mai gudanarwa ko sa hannun HMAC-SHA256 ke ba da izini.

Amintacce ta tsohuwa — ba a taba adana shafuka masu kuzari ba

Caching mai tsauri yana da aminci ne kawai idan abubuwan da dole ne su ci gaba da kasancewa a buɗe ba a taɓa yin caching dinsu ba. Zinn® Cache yana zuwa tare da tsoffin saitunan WordPress da WooCommerce / Easy Digital Downloads masu dacewa: an cire kwando, wurin biya, my-account, REST da AJAX, samfoti da bincike, kuma kowace buƙata ta mai shiga ko mai kuki na zama ana ba da ita sabuwa.

Wannan yana nufin mai siye ba zai taba ganin keken wani ba kuma editan da ya shiga ba zai taba ganin tsohon daftari ba. Kuna iya ƙarin ƙarin hanya, maɓallin tambaya da dokokin kariyar kuki a kowane shafi lokacin da wani kari ke buƙatar su, ba tare da taɓa tsoffin tsarin tsaro ba.

Ajiye a madubin bayanai (Caching) abu ne da ya shafi kowane tsari (blueprint) daban, don haka rukunin shafukan static, PHP, da Node za su sami tsarin ajiye bayanai da ya dace da su, kuma kariyar (plugin) za ta yi aiki yadda ya kamata a ko da ya waje babu wani tsari na ajiye shafi gaba ɗaya.

Tambayoyi akai-akai

Shin dole ne in saita kowane daga cikin Wannan?

A'a. Filogin Zinn® Cache yana zuwa tare da footprint na turawa kuma an saita cache na shafi guda, cache na abu, sharewa ta atomatik, da keɓewa amintattu a kan shafukan da Zinn® ke ɗaukar nauyi ta atomatik. Kuna iya daidaita komai a ƙasa da Settings → Zinn® Cache, ko daga allon sarrafawa, idan kuna so.

Shin caching zai lalatar da kantina na WooCommerce?

Babu. Ba a taba adana fakon shafi (cache) na Cart, checkout, my-account, da kowane buƙatar shiga ko zaman (session-cookie) ta tsohuwa ba, don haka shafuka masu sauyawa da na kowane abokin ciniki koyaushe suna kasancewa a buɗe. Fakon shafin gabaɗaya yana ba da shafuka ne kawai waɗanda suke da daidai da kowane baƙo.

Me ke faruwa idan Redis ba ya nan?

Boye abubuwa da aka kirkira na osfanal ne kuma baya haifar da matsala idan ya fadi. Idan ba a samu fadada phpredis ba, ana nakasa maballin tare da sanarwa; idan aka rasa hanyar sadarwa da Redis yayin gudanarwa, drop-in din yana amfani da boye abubuwa na in-memory na kowace bukata domin gidan yanar gizon kar ya taba daina aiki.

Ana buƙatar LiteSpeed?

Caching shafi gaba ɗaya yana amfani da uwar garken yanar gizo na LiteSpeed, ko kuma kari na LiteSpeed Cache na ɓangare na uku idan ya riga ya yi aiki. A sauran uwar garken ba a fitar da taken cache ba, amma cache abu, keɓewa, da sharewa daga nesa duk suna ci gaba da aiki.

Ta yaya cache na CDN da na uwar garken suke kasancewa a tare?

Tsabtace mai jituwa guda ɗaya. Lokacin da abun ciki ya canza, tsabtace ta musamman ta tag tana share shafukan da abin ya shafa a uwar garken gidan yanar gizo kuma ana nuna su zuwa CDN da baki ta hanyar signed webhook, don haka kowane Layer yana share shafuka guda ɗaya a lokaci guda.

Mai alaƙa

Ka gani a kan naku shafukan

Fara gwaji na kwanaki 14 ba tare da katin bashi ba kuma bari aikin cache mai matakai da yawa ya yi aiki. Canja wuri kyauta, garantin dawo da kudi na kwanaki 30, tabbacin kasancewa kan layin yanar gizo na kashi 99.99% kuma babu takurawa daga mai ba da sabis.

Fara kyauta