{"id":4338,"date":"2026-02-03T12:40:55","date_gmt":"2026-02-03T09:40:55","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/wordpress-blog-woocommerce-ve-saas-icin-kac-cpu-ne-kadar-ram\/"},"modified":"2026-02-03T12:40:55","modified_gmt":"2026-02-03T09:40:55","slug":"wordpress-blog-woocommerce-ve-saas-icin-kac-cpu-ne-kadar-ram","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/wordpress-blog-woocommerce-ve-saas-icin-kac-cpu-ne-kadar-ram\/","title":{"rendered":"WordPress Blog, WooCommerce ve SaaS \u0130\u00e7in Ka\u00e7 CPU, Ne Kadar RAM?"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><p>Yeni bir WordPress blog, WooCommerce ma\u011faza ya da SaaS \u00fcr\u00fcn\u00fc planlarken en \u00e7ok tak\u0131lan noktalardan biri \u015fudur: &#8220;Ka\u00e7 CPU almal\u0131y\u0131m, ne kadar RAM yeter?&#8221; Proje toplant\u0131lar\u0131nda b\u00fct\u00e7e konu\u015fulurken \u00e7o\u011fu zaman tasar\u0131m, \u00f6zellik listesi ve pazarlama detayl\u0131 konu\u015fulur; altyap\u0131 taraf\u0131 ise &#8220;\u015fimdilik k\u00fc\u00e7\u00fck bir <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> al\u0131r\u0131z, b\u00fcy\u00fcrse bakar\u0131z&#8221; seviyesinde kal\u0131r. Sonra ilk kampanyada site yava\u015flar, \u00f6deme ad\u0131mlar\u0131 tak\u0131l\u0131r, dashboard ekranlar\u0131 saniyelerce d\u00f6ner ve konu ister istemez acil kriz toplant\u0131s\u0131na d\u00f6ner.<\/p>\n<p>Bu yaz\u0131da DCHost ekibi olarak y\u0131llard\u0131r sahada g\u00f6rd\u00fc\u011f\u00fcm\u00fcz ger\u00e7ek senaryolardan yola \u00e7\u0131k\u0131p; WordPress blog, WooCommerce ve k\u00fc\u00e7\u00fck\/orta \u00f6l\u00e7ekli SaaS uygulamalar\u0131 i\u00e7in VPS taraf\u0131nda <strong>ka\u00e7 CPU<\/strong>, <strong>ne kadar RAM<\/strong> ve nas\u0131l bir yakla\u015f\u0131m gerekli, ad\u0131m ad\u0131m netle\u015ftirece\u011fiz. Amac\u0131m\u0131z &#8220;ezber de\u011ferler&#8221; \u00f6nermekten \u00e7ok, kendi projenizi oturup hesaplayabilece\u011finiz pratik bir \u00e7er\u00e7eve vermek. B\u00f6ylece hem gere\u011finden b\u00fcy\u00fck sunucuya gereksiz para \u00f6demez, hem de trafik geldi\u011finde bo\u011fulan bir projeyle u\u011fra\u015fmak zorunda kalmazs\u0131n\u0131z.<\/p>\n<div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#CPU_ve_RAM_Temel_Mantigi_vCPU_Is_Parcacigi_ve_Bellek_Tuketimi\"><span class=\"toc_number toc_depth_1\">1<\/span> CPU ve RAM Temel Mant\u0131\u011f\u0131: vCPU, \u0130\u015f Par\u00e7ac\u0131\u011f\u0131 ve Bellek T\u00fcketimi<\/a><\/li><li><a href=\"#WordPress_Blog_Icin_Kac_CPU_Ne_Kadar_RAM\"><span class=\"toc_number toc_depth_1\">2<\/span> WordPress Blog \u0130\u00e7in Ka\u00e7 CPU, Ne Kadar RAM?<\/a><ul><li><a href=\"#Kucuk_Kisisel_Blog_Gunluk_5002000_Ziyaret\"><span class=\"toc_number toc_depth_2\">2.1<\/span> K\u00fc\u00e7\u00fck Ki\u015fisel Blog (G\u00fcnl\u00fck 500\u20132.000 Ziyaret)<\/a><\/li><li><a href=\"#Orta_Olcekli_Icerik_Sitesi_Gunluk_500020000_Ziyaret\"><span class=\"toc_number toc_depth_2\">2.2<\/span> Orta \u00d6l\u00e7ekli \u0130\u00e7erik Sitesi (G\u00fcnl\u00fck 5.000\u201320.000 Ziyaret)<\/a><\/li><li><a href=\"#Yuksek_Trafikli_Haber_Blog_Gunluk_20000100000_Ziyaret\"><span class=\"toc_number toc_depth_2\">2.3<\/span> Y\u00fcksek Trafikli Haber \/ Blog (G\u00fcnl\u00fck 20.000\u2013100.000+ Ziyaret)<\/a><\/li><\/ul><\/li><li><a href=\"#WooCommerce_Magazalar_Icin_CPU_ve_RAM_Hesabi\"><span class=\"toc_number toc_depth_1\">3<\/span> WooCommerce Ma\u011fazalar \u0130\u00e7in CPU ve RAM Hesab\u0131<\/a><ul><li><a href=\"#Mikro_Magaza_Gunluk_50200_Siparis\"><span class=\"toc_number toc_depth_2\">3.1<\/span> Mikro Ma\u011faza (G\u00fcnl\u00fck 50\u2013200 Sipari\u015f)<\/a><\/li><li><a href=\"#Buyuyen_ETicaret_Gunluk_2001000_Siparis\"><span class=\"toc_number toc_depth_2\">3.2<\/span> B\u00fcy\u00fcyen E\u2011Ticaret (G\u00fcnl\u00fck 200\u20131.000 Sipari\u015f)<\/a><\/li><li><a href=\"#Kampanya_ve_Sezonluk_Trafik_Patlamalari\"><span class=\"toc_number toc_depth_2\">3.3<\/span> Kampanya ve Sezonluk Trafik Patlamalar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#SaaS_Uygulamalari_Icin_CPU_ve_RAM_Planlama_Yaklasimi\"><span class=\"toc_number toc_depth_1\">4<\/span> SaaS Uygulamalar\u0131 \u0130\u00e7in CPU ve RAM Planlama Yakla\u015f\u0131m\u0131<\/a><ul><li><a href=\"#MVP_EarlyStage_SaaS_Ilk_50100_Musteri\"><span class=\"toc_number toc_depth_2\">4.1<\/span> MVP \/ Early\u2011Stage SaaS (\u0130lk 50\u2013100 M\u00fc\u015fteri)<\/a><\/li><li><a href=\"#100500_Aktif_Eszamanli_Kullanici_Seviyesi\"><span class=\"toc_number toc_depth_2\">4.2<\/span> 100\u2013500 Aktif E\u015fzamanl\u0131 Kullan\u0131c\u0131 Seviyesi<\/a><\/li><li><a href=\"#Istek_Basina_Kaynak_Tuketimi_Mantigi\"><span class=\"toc_number toc_depth_2\">4.3<\/span> \u0130stek Ba\u015f\u0131na Kaynak T\u00fcketimi Mant\u0131\u011f\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#RAM_Hesabi_PHP-FPM_Veritabani_ve_Cachein_Payini_Bolmek\"><span class=\"toc_number toc_depth_1\">5<\/span> RAM Hesab\u0131: PHP-FPM, Veritaban\u0131 ve Cache\u2019in Pay\u0131n\u0131 B\u00f6lmek<\/a><\/li><li><a href=\"#Kaynak_Planlamayi_Adim_Adim_Hesaplama_Pratik_Cerceve\"><span class=\"toc_number toc_depth_1\">6<\/span> Kaynak Planlamay\u0131 Ad\u0131m Ad\u0131m Hesaplama: Pratik \u00c7er\u00e7eve<\/a><ul><li><a href=\"#1_Trafik_ve_Kullanici_Davranisini_Tahmin_Et\"><span class=\"toc_number toc_depth_2\">6.1<\/span> 1. Trafik ve Kullan\u0131c\u0131 Davran\u0131\u015f\u0131n\u0131 Tahmin Et<\/a><\/li><li><a href=\"#2_Sayfa_Turlerine_Gore_Dinamik_Istek_Yukunu_Belirle\"><span class=\"toc_number toc_depth_2\">6.2<\/span> 2. Sayfa T\u00fcrlerine G\u00f6re Dinamik \u0130stek Y\u00fck\u00fcn\u00fc Belirle<\/a><\/li><li><a href=\"#3_vCPU_Hesabi_Eszamanli_Istek_ve_Islem_Suresi\"><span class=\"toc_number toc_depth_2\">6.3<\/span> 3. vCPU Hesab\u0131: E\u015fzamanl\u0131 \u0130stek ve \u0130\u015flem S\u00fcresi<\/a><\/li><li><a href=\"#4_RAM_Hesabi_Bilesenlere_Kota_Tanimla\"><span class=\"toc_number toc_depth_2\">6.4<\/span> 4. RAM Hesab\u0131: Bile\u015fenlere Kota Tan\u0131mla<\/a><\/li><\/ul><\/li><li><a href=\"#Sik_Yapilan_Hatalar_ve_Guvenli_Pay_Birakma_Stratejisi\"><span class=\"toc_number toc_depth_1\">7<\/span> S\u0131k Yap\u0131lan Hatalar ve G\u00fcvenli Pay B\u0131rakma Stratejisi<\/a><ul><li><a href=\"#8220Simdilik_En_Kucugu_Yeter8221_Yaklasimi\"><span class=\"toc_number toc_depth_2\">7.1<\/span> &#8220;\u015eimdilik En K\u00fc\u00e7\u00fc\u011f\u00fc Yeter&#8221; Yakla\u015f\u0131m\u0131<\/a><\/li><li><a href=\"#Surekli_8090_CPU_Kullanimini_8220Kaynaklar_Bosa_Gitmesin8221_Diye_Normallestirmek\"><span class=\"toc_number toc_depth_2\">7.2<\/span> S\u00fcrekli %80\u201390 CPU Kullan\u0131m\u0131n\u0131 &#8220;Kaynaklar Bo\u015fa Gitmesin&#8221; Diye Normalle\u015ftirmek<\/a><\/li><li><a href=\"#RAMi_Swap_ile_Telafi_Edebilecegini_Dusunmek\"><span class=\"toc_number toc_depth_2\">7.3<\/span> RAM\u2019i Swap ile Telafi Edebilece\u011fini D\u00fc\u015f\u00fcnmek<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_Uzerinde_Pratik_Planlama_Blog_WooCommerce_ve_SaaS\"><span class=\"toc_number toc_depth_1\">8<\/span> DCHost \u00dczerinde Pratik Planlama: Blog, WooCommerce ve SaaS<\/a><\/li><li><a href=\"#Ozet_ve_Sonraki_Adimlar\"><span class=\"toc_number toc_depth_1\">9<\/span> \u00d6zet ve Sonraki Ad\u0131mlar<\/a><\/li><\/ul><\/div>\n<h2><span id=\"CPU_ve_RAM_Temel_Mantigi_vCPU_Is_Parcacigi_ve_Bellek_Tuketimi\">CPU ve RAM Temel Mant\u0131\u011f\u0131: vCPU, \u0130\u015f Par\u00e7ac\u0131\u011f\u0131 ve Bellek T\u00fcketimi<\/span><\/h2>\n<p>Detayl\u0131 senaryolara ge\u00e7meden \u00f6nce, VPS taraf\u0131nda CPU ve RAM\u2019in ne anlama geldi\u011fini netle\u015ftirelim. DCHost \u00fczerinde ald\u0131\u011f\u0131n\u0131z bir VPS\u2019te tipik olarak <strong>vCPU<\/strong> (sanal CPU \u00e7ekirde\u011fi) ve <strong>GB cinsinden RAM<\/strong> g\u00f6r\u00fcrs\u00fcn\u00fcz.<\/p>\n<ul>\n<li><strong>vCPU<\/strong>: Fiziksel i\u015flemcinin payla\u015ft\u0131r\u0131lm\u0131\u015f mant\u0131ksal \u00e7ekirdekleridir. Web taraf\u0131nda d\u00fc\u015f\u00fcnebilece\u011finiz en basit kar\u015f\u0131l\u0131k, ayn\u0131 anda \u00e7al\u0131\u015fabilecek PHP-FPM veya uygulama i\u015f par\u00e7ac\u0131\u011f\u0131 (worker) say\u0131s\u0131d\u0131r.<\/li>\n<li><strong>RAM<\/strong>: Uygulaman\u0131z\u0131n, veritaban\u0131n\u0131z\u0131n ve i\u015fletim sisteminin bellekte tuttu\u011fu her \u015feyin toplam alan\u0131. RAM bitti\u011finde sistem SWAP\u2019e d\u00fc\u015fer, bu da \u00f6zellikle NVMe olmayan sistemlerde ciddi yava\u015flama ve hatta <em>OOM killer<\/em> ile servislerin kapanmas\u0131na kadar gider.<\/li>\n<\/ul>\n<p>CPU genelde <strong>ani y\u00fcklerde<\/strong> bo\u011fulur (kampanya, haber patlamas\u0131, yo\u011fun API trafi\u011fi), RAM ise <strong>s\u00fcrekli birikim<\/strong> problemi gibi davran\u0131r (cache \u015fi\u015fmesi, PHP-FPM prosesleri, b\u00fcy\u00fcyen veritaban\u0131 buffer\u2019lar\u0131). Bu y\u00fczden ikisini birlikte d\u00fc\u015f\u00fcnmek gerekir.<\/p>\n<p>VPS kaynaklar\u0131n\u0131 nas\u0131l izleyece\u011finizi ve hangi metriklere bakman\u0131z gerekti\u011fini ayr\u0131nt\u0131l\u0131 g\u00f6rmek isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/vps-kaynak-kullanimi-izleme-rehberi-htop-iotop-netdata-ve-prometheus\/\">VPS kaynak kullan\u0131m\u0131 izleme rehberi<\/a> yaz\u0131m\u0131z\u0131 da mutlaka okuman\u0131z\u0131 \u00f6neririm.<\/p>\n<h2><span id=\"WordPress_Blog_Icin_Kac_CPU_Ne_Kadar_RAM\">WordPress Blog \u0130\u00e7in Ka\u00e7 CPU, Ne Kadar RAM?<\/span><\/h2>\n<p>WordPress blog taraf\u0131nda en kritik parametreler; e\u015fzamanl\u0131 ziyaret\u00e7i say\u0131s\u0131, kullan\u0131lan tema\/eklenti a\u011f\u0131rl\u0131\u011f\u0131 ve \u00f6nbellekleme stratejinizdir. Ayn\u0131 ziyaret\u00e7i say\u0131s\u0131nda bile, hafif bir tema + iyi bir cache kurgusu ile kaynak t\u00fcketimi dramatik \u015fekilde d\u00fc\u015fer.<\/p>\n<h3><span id=\"Kucuk_Kisisel_Blog_Gunluk_5002000_Ziyaret\">K\u00fc\u00e7\u00fck Ki\u015fisel Blog (G\u00fcnl\u00fck 500\u20132.000 Ziyaret)<\/span><\/h3>\n<p>Senaryo: Standart bir WordPress kurulumu, hafif bir tema, birka\u00e7 temel eklenti (SEO, cache, g\u00fcvenlik). G\u00fcnl\u00fck 500\u20132.000 civar\u0131 ziyaret, e\u015fzamanl\u0131 5\u201315 kullan\u0131c\u0131.<\/p>\n<ul>\n<li><strong>\u00d6nerilen minimum VPS<\/strong>: 1 vCPU, 1 GB RAM<\/li>\n<li><strong>Konforlu ba\u015flang\u0131\u00e7<\/strong>: 1\u20132 vCPU, 2 GB RAM<\/li>\n<\/ul>\n<p>1 vCPU, d\u00fczg\u00fcn yap\u0131land\u0131r\u0131lm\u0131\u015f bir PHP-FPM ve tam sayfa \u00f6nbellekleme ile (LiteSpeed Cache, Nginx FastCGI cache vb.) bu \u00f6l\u00e7ek i\u00e7in \u00e7o\u011fu zaman yeterlidir. RAM taraf\u0131nda ise 1 GB alt\u0131, servisler ve i\u015fletim sistemi pay\u0131n\u0131 da d\u00fc\u015f\u00fcn\u00fcnce risklidir. 2 GB RAM, MySQL\/MariaDB ve PHP-FPM i\u00e7in \u00e7ok daha rahat bir alan sa\u011flar.<\/p>\n<p>WordPress taraf\u0131nda PHP-FPM, OPcache ve Redis gibi bile\u015fenleri do\u011fru ayarlad\u0131\u011f\u0131n\u0131zda ayn\u0131 donan\u0131mdan \u00e7ok daha fazla verim alabilirsiniz. Detayl\u0131 sunucu taraf\u0131 ayarlar\u0131 i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/wordpress-icin-sunucu-tarafi-optimizasyon-php-fpm-opcache-redis-ve-mysql-ile-neyi-ne-zaman-nasil-ayarlamalisin\/\">WordPress i\u00e7in sunucu taraf\u0131 optimizasyon rehberi<\/a> size iyi bir rehber olacakt\u0131r.<\/p>\n<h3><span id=\"Orta_Olcekli_Icerik_Sitesi_Gunluk_500020000_Ziyaret\">Orta \u00d6l\u00e7ekli \u0130\u00e7erik Sitesi (G\u00fcnl\u00fck 5.000\u201320.000 Ziyaret)<\/span><\/h3>\n<p>Senaryo: Kategorili i\u00e7erik sitesi, hafif trafik patlamalar\u0131, sosyal medyadan gelen dalgal\u0131 trafik. E\u015fzamanl\u0131 30\u2013100 kullan\u0131c\u0131, yo\u011fun zamanlarda 200\u2019e pik.<\/p>\n<ul>\n<li><strong>\u00d6nerilen ba\u015flang\u0131\u00e7<\/strong>: 2 vCPU, 4 GB RAM<\/li>\n<li><strong>Yo\u011fun yay\u0131n yapanlar i\u00e7in<\/strong>: 4 vCPU, 8 GB RAM<\/li>\n<\/ul>\n<p>Bu \u00f6l\u00e7ekte as\u0131l fark\u0131 yaratanlar:<\/p>\n<ul>\n<li>\u0130yi bir tam sayfa cache (anonim kullan\u0131c\u0131lar\u0131n \u00e7o\u011funu cache\u2019den beslemek)<\/li>\n<li>Veritaban\u0131 sorgular\u0131n\u0131 \u00e7ok yormayan tema\/eklenti se\u00e7imi<\/li>\n<li>Medya dosyalar\u0131n\u0131 CDN veya object storage\u2019a offload etmek<\/li>\n<\/ul>\n<p>E\u011fer haber tarz\u0131, \u00e7ok s\u0131k g\u00fcncellenen i\u00e7erikler yay\u0131nl\u0131yorsan\u0131z, cache s\u00fcresini do\u011fru dengelemek ve veritaban\u0131 y\u00fck\u00fcn\u00fc hafifletmek kritik hale gelir. <a href=\"https:\/\/www.dchost.com\/blog\/yuksek-trafikli-haber-ve-blog-siteleri-icin-hosting-onbellek-cdn-ve-veritabani-olceklendirme\/\">Y\u00fcksek trafikli haber ve blog siteleri i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z detayl\u0131 rehber<\/a> bu noktada g\u00fczel bir tamamlay\u0131c\u0131 olacakt\u0131r.<\/p>\n<h3><span id=\"Yuksek_Trafikli_Haber_Blog_Gunluk_20000100000_Ziyaret\">Y\u00fcksek Trafikli Haber \/ Blog (G\u00fcnl\u00fck 20.000\u2013100.000+ Ziyaret)<\/span><\/h3>\n<p>Senaryo: Birden \u00e7ok edit\u00f6r, s\u0131k i\u00e7erik giri\u015fi, anl\u0131k trafik patlamalar\u0131 (g\u00fcndem haberleri, kampanyalar). E\u015fzamanl\u0131 200\u20131.000+ kullan\u0131c\u0131.<\/p>\n<ul>\n<li><strong>Ba\u015flang\u0131\u00e7 noktas\u0131<\/strong>: 4 vCPU, 8 GB RAM, NVMe disk<\/li>\n<li><strong>Daha agresif senaryolar<\/strong>: 6\u20138 vCPU, 12\u201316 GB RAM<\/li>\n<\/ul>\n<p>Bu seviyede art\u0131k sadece CPU ve RAM de\u011fil, <strong>disk IOPS<\/strong> (\u00f6zellikle MySQL\/MariaDB i\u00e7in) ve <strong>a\u011f gecikmesi<\/strong> de oyuna girer. NVMe diskler, rastgele okuma\/yazma performanslar\u0131 sayesinde veritaban\u0131 y\u00fck\u00fcnde ciddi fark yarat\u0131r. Ayr\u0131ca:<\/p>\n<ul>\n<li>Redis\/Memcached ile nesne \u00f6nbelle\u011fi<\/li>\n<li>Query cache yerine do\u011fru indekslenmi\u015f veritaban\u0131<\/li>\n<li>Statik dosyalar i\u00e7in bir CDN katman\u0131<\/li>\n<\/ul>\n<p>E\u011fer bu seviyedeyseniz, sadece tek VPS de\u011fil; veritaban\u0131n\u0131 ayr\u0131 bir sunucuya alma, replikasyon ve cache katmanlar\u0131n\u0131 da konu\u015fmak anlaml\u0131 olmaya ba\u015flar.<\/p>\n<h2><span id=\"WooCommerce_Magazalar_Icin_CPU_ve_RAM_Hesabi\">WooCommerce Ma\u011fazalar \u0130\u00e7in CPU ve RAM Hesab\u0131<\/span><\/h2>\n<p>WooCommerce, d\u00fcz bir blog\u2019a g\u00f6re \u00e7ok daha a\u011f\u0131r bir i\u015f y\u00fck\u00fcd\u00fcr. \u00c7\u00fcnk\u00fc:<\/p>\n<ul>\n<li>Sepete ekleme, kupon, stok kontrol\u00fc, kargo hesaplama gibi i\u015flemler dinamik ve CPU maliyetlidir.<\/li>\n<li>Her sipari\u015f veritaban\u0131na \u00e7ok daha fazla yazma operasyonu yapar.<\/li>\n<li>\u00d6deme sayfalar\u0131 genelde cache\u2019lenemez; her istek ger\u00e7ek PHP \u00e7al\u0131\u015ft\u0131r\u0131r.<\/li>\n<\/ul>\n<p>Bu y\u00fczden g\u00fcnl\u00fck ziyaret\u00e7i say\u0131s\u0131 ayn\u0131 olsa bile, WooCommerce genelde bir blog\u2019dan <strong>en az 2 kat<\/strong> daha agresif kaynak t\u00fcketir. Detayl\u0131 form\u00fcller ve \u00f6rnekler i\u00e7in ayr\u0131ca <a href=\"https:\/\/www.dchost.com\/blog\/woocommerce-kapasite-planlama-rehberi-vcpu-ram-iops-nasil-hesaplanir\/\">WooCommerce kapasite planlama rehberi<\/a> yaz\u0131m\u0131za da g\u00f6z atabilirsiniz.<\/p>\n<h3><span id=\"Mikro_Magaza_Gunluk_50200_Siparis\">Mikro Ma\u011faza (G\u00fcnl\u00fck 50\u2013200 Sipari\u015f)<\/span><\/h3>\n<p>Senaryo: Yeni a\u00e7\u0131lm\u0131\u015f butik ma\u011faza, s\u0131n\u0131rl\u0131 \u00fcr\u00fcn say\u0131s\u0131 (50\u2013200 \u00fcr\u00fcn), ayn\u0131 anda genellikle 10\u201330 ziyaret\u00e7i, zaman zaman 50\u201360\u2019a \u00e7\u0131kan pikler.<\/p>\n<ul>\n<li><strong>\u00d6nerilen ba\u015flang\u0131\u00e7<\/strong>: 2 vCPU, 4 GB RAM, NVMe disk<\/li>\n<li><strong>Daha rahat alan isteyenler i\u00e7in<\/strong>: 3\u20134 vCPU, 6\u20138 GB RAM<\/li>\n<\/ul>\n<p>Burada as\u0131l s\u0131k\u0131nt\u0131, kampanya veya influencer payla\u015f\u0131m\u0131 gibi beklenmedik anl\u0131k piklerdir. Normalde CPU %15\u201320 seyrederken, bir anda checkout sayfas\u0131nda onlarca e\u015fzamanl\u0131 kullan\u0131c\u0131 g\u00f6rebilirsiniz. 2 vCPU bu tip ani y\u00fckleri \u00e7ok b\u00fcy\u00fcmeden kar\u015f\u0131layabilir, ancak <strong>4 GB RAM<\/strong> alt\u0131na d\u00fc\u015fmemek sipari\u015f yo\u011funlu\u011funda veritaban\u0131 ve PHP s\u00fcre\u00e7lerinin s\u0131k\u0131\u015fmamas\u0131 i\u00e7in kritiktir.<\/p>\n<h3><span id=\"Buyuyen_ETicaret_Gunluk_2001000_Siparis\">B\u00fcy\u00fcyen E\u2011Ticaret (G\u00fcnl\u00fck 200\u20131.000 Sipari\u015f)<\/span><\/h3>\n<p>Senaryo: Orta \u00f6l\u00e7ekli e\u2011ticaret sitesi, binlerce \u00fcr\u00fcn, yo\u011fun kategori\/filtre kullan\u0131m\u0131, entegrasyonlar (pazaryeri, muhasebe, kargo vs.). E\u015fzamanl\u0131 100\u2013400 kullan\u0131c\u0131.<\/p>\n<ul>\n<li><strong>\u00d6nerilen mimari (tek VPS\u2019te ba\u015flarken)<\/strong>: 4 vCPU, 8 GB RAM, y\u00fcksek IOPS\u2019lu NVMe disk<\/li>\n<li><strong>B\u00fcy\u00fcmeye haz\u0131r mimari<\/strong>: 6\u20138 vCPU, 12\u201316 GB RAM ve veritaban\u0131n\u0131 ayr\u0131 VPS\u2019e ay\u0131rma plan\u0131<\/li>\n<\/ul>\n<p>Bu \u00f6l\u00e7ekten itibaren \u015fu konular\u0131 da masaya koyman\u0131z gerekir:<\/p>\n<ul>\n<li>MySQL\/MariaDB i\u00e7in ayr\u0131 sunucuya ge\u00e7mek <a href=\"https:\/\/www.dchost.com\/blog\/veritabani-sunucusunu-uygulama-sunucusundan-ayirmak-ne-zaman-mantiklli\/\">veritaban\u0131n\u0131 uygulama sunucusundan ay\u0131rman\u0131n mant\u0131kl\u0131 oldu\u011fu e\u015fiklerden<\/a> biridir.<\/li>\n<li>WooCommerce i\u00e7in \u00f6zel veritaban\u0131 indeksleme ve sorgu optimizasyonu (<a href=\"https:\/\/www.dchost.com\/blog\/woocommerce-ve-buyuk-katalog-siteleri-icin-mysql-indeksleme-ve-sorgu-optimizasyonu-rehberi\/\">detayl\u0131 rehber<\/a>te anlatt\u0131\u011f\u0131m\u0131z gibi) ciddi CPU kazand\u0131r\u0131r.<\/li>\n<li>Redis tabanl\u0131 nesne \u00f6nbelle\u011fi ve tam sayfa cache, \u00f6zellikle anonim trafik taraf\u0131nda CPU y\u00fck\u00fcn\u00fc dramatik azalt\u0131r.<\/li>\n<\/ul>\n<h3><span id=\"Kampanya_ve_Sezonluk_Trafik_Patlamalari\">Kampanya ve Sezonluk Trafik Patlamalar\u0131<\/span><\/h3>\n<p>WooCommerce taraf\u0131nda en \u00e7ok can yakan \u015fey planlanmam\u0131\u015f kampanya pikleridir. Normalde yeterli olan kaynaklar, 2\u20133 kat trafik art\u0131\u015f\u0131nda bo\u011fulabilir. Bu y\u00fczden kapasite planlarken her zaman:<\/p>\n<ul>\n<li>Normal g\u00fcn CPU\/RAM y\u00fck\u00fcn\u00fcn en fazla %60\u201370 civar\u0131nda kalmas\u0131n\u0131<\/li>\n<li>Kampanya g\u00fcnlerinde ise k\u0131sa s\u00fcreli %80\u201390 piklerini tolere edebilecek rezerviniz olmas\u0131n\u0131<\/li>\n<\/ul>\n<p>hedeflemek sa\u011fl\u0131kl\u0131d\u0131r. \u00d6zellikle kampanya bazl\u0131 \u00e7al\u0131\u015fan e\u2011ticaret projeleri i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/sezonluk-trafik-patlamalarina-hazirlik-hosting-olcekleme-onbellek-ve-okunur-mod-stratejileri\/\">sezonluk trafik patlamalar\u0131na haz\u0131rl\u0131k rehberi<\/a>ndeki \u00f6nbellek ve \u00f6l\u00e7ekleme stratejilerini uygulaman\u0131z\u0131 \u00f6neririz.<\/p>\n<h2><span id=\"SaaS_Uygulamalari_Icin_CPU_ve_RAM_Planlama_Yaklasimi\">SaaS Uygulamalar\u0131 \u0130\u00e7in CPU ve RAM Planlama Yakla\u015f\u0131m\u0131<\/span><\/h2>\n<p>SaaS d\u00fcnyas\u0131nda i\u015f y\u00fck\u00fc WordPress\/WooCommerce\u2019e g\u00f6re \u00e7ok daha de\u011fi\u015fken ve uygulama mimarisine ba\u011f\u0131ml\u0131d\u0131r. Yine de birka\u00e7 tipik senaryodan hareketle bir \u00e7er\u00e7eve \u00e7izebiliriz.<\/p>\n<h3><span id=\"MVP_EarlyStage_SaaS_Ilk_50100_Musteri\">MVP \/ Early\u2011Stage SaaS (\u0130lk 50\u2013100 M\u00fc\u015fteri)<\/span><\/h3>\n<p>Senaryo: Tek VPS \u00fczerinde \u00e7al\u0131\u015fan monolitik bir PHP\/Laravel, Node.js veya benzeri uygulama. Ayn\u0131 anda aktif 10\u201350 kullan\u0131c\u0131, arka planda \u00e7al\u0131\u015fan s\u0131n\u0131rl\u0131 say\u0131da cron\/queue i\u015fi.<\/p>\n<ul>\n<li><strong>\u00d6nerilen ba\u015flang\u0131\u00e7<\/strong>: 2 vCPU, 4 GB RAM<\/li>\n<li><strong>Daha g\u00fcvenli alan<\/strong>: 3\u20134 vCPU, 6\u20138 GB RAM<\/li>\n<\/ul>\n<p>Burada \u00f6nemli olan, ilk g\u00fcnden mikro servis mimarisine girmek de\u011fil, tek bir orta boy VPS \u00fczerinde:<\/p>\n<ul>\n<li>Uygulama proseslerini (PHP-FPM, Node.js worker\u2019lar\u0131 vb.) mant\u0131kl\u0131 say\u0131da tutmak<\/li>\n<li>Veritaban\u0131 ve cache (Redis vb.) i\u00e7in yeterli RAM b\u0131rakmak<\/li>\n<li>Queue\/cron i\u015flerini web isteklerinden ay\u0131rmak<\/li>\n<\/ul>\n<p>K\u00fc\u00e7\u00fck SaaS projeleri i\u00e7in tek VPS, \u00e7oklu VPS ve y\u00f6netilen bulut senaryolar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131rd\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/kucuk-saas-uygulamalari-icin-en-dogru-hosting-mimarisi-tek-vps-coklu-vps-ve-yonetilen-bulut\/\">SaaS i\u00e7in en do\u011fru hosting mimarisi<\/a> yaz\u0131s\u0131na da g\u00f6z atabilirsiniz.<\/p>\n<h3><span id=\"100500_Aktif_Eszamanli_Kullanici_Seviyesi\">100\u2013500 Aktif E\u015fzamanl\u0131 Kullan\u0131c\u0131 Seviyesi<\/span><\/h3>\n<p>Senaryo: Art\u0131k onlarca de\u011fil, y\u00fczlerce aktif oturumun ayn\u0131 anda panel, rapor ekranlar\u0131 veya ger\u00e7ek zamanl\u0131 bile\u015fenlerle sistemi kulland\u0131\u011f\u0131 noktadas\u0131n\u0131z. Arka planda yo\u011fun queue i\u015fleri (raporlama, entegrasyon, PDF olu\u015fturma vb.) \u00e7al\u0131\u015f\u0131yor.<\/p>\n<ul>\n<li><strong>\u00d6nerilen kaynak band\u0131<\/strong>: 4\u20138 vCPU, 8\u201316 GB RAM<\/li>\n<li><strong>Mimari \u00f6neriler<\/strong>:<\/li>\n<\/ul>\n<ul>\n<li>Veritaban\u0131n\u0131 ayr\u0131 bir VPS\u2019e ta\u015f\u0131ma<\/li>\n<li>Queue\/worker s\u00fcre\u00e7leri i\u00e7in ayr\u0131 bir VPS ya da en az\u0131ndan ayr\u0131 CPU havuzu<\/li>\n<li>Redis\/Memcached ile session ve cache y\u00f6netimini diske b\u0131rakmamak<\/li>\n<\/ul>\n<p>Bu seviyede &#8220;her \u015feyi tek VPS\u2019e y\u0131\u011fma&#8221; stratejisi k\u0131sa s\u00fcrede t\u0131kan\u0131r. Y\u00fck\u00fc uygulama, veritaban\u0131 ve background i\u015fler olarak ay\u0131r\u0131p, her katman i\u00e7in ayr\u0131 CPU\/RAM planlamak \u00e7ok daha sa\u011fl\u0131kl\u0131 ilerlemenizi sa\u011flar. \u00c7ok kirac\u0131l\u0131 (multi\u2011tenant) SaaS mimarileri ve do\u011fru altyap\u0131 se\u00e7imleri i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/saas-uygulamalari-icin-cok-kiracili-mimari-turleri-ve-dogru-hosting-altyapisi-secimi\/\">bu kapsaml\u0131 SaaS rehberimizi<\/a> de inceleyebilirsiniz.<\/p>\n<h3><span id=\"Istek_Basina_Kaynak_Tuketimi_Mantigi\">\u0130stek Ba\u015f\u0131na Kaynak T\u00fcketimi Mant\u0131\u011f\u0131<\/span><\/h3>\n<p>SaaS\u2019ta kaba bir hesap yapmak i\u00e7in \u015fu d\u00fc\u015f\u00fcnce deneyini kullanabilirsiniz:<\/p>\n<ol>\n<li>Uygulaman\u0131zda tipik bir sayfa iste\u011finin CPU\u2019da ne kadar s\u00fcrd\u00fc\u011f\u00fcn\u00fc \u00f6l\u00e7\u00fcn (\u00f6rne\u011fin 50 ms).<\/li>\n<li>Bir saniyede bir vCPU teorik olarak 1.000 ms i\u015flem yapabilir. 50 ms\u2019lik i\u015flemler i\u00e7in bu, saniyede 20 istek kapasitesi demektir.<\/li>\n<li>4 vCPU i\u00e7in teorik \u00fcst s\u0131n\u0131r saniyede 80 istektir. Ger\u00e7ekte bunun %50\u201360\u2019\u0131n\u0131 g\u00fcvenli kabul edin.<\/li>\n<\/ol>\n<p>B\u00f6ylece, beklenen e\u015fzamanl\u0131 kullan\u0131c\u0131 ve istek say\u0131s\u0131ndan yola \u00e7\u0131karak, kabaca ka\u00e7 vCPU\u2019ya ihtiyac\u0131n\u0131z oldu\u011funu tahmin edebilirsiniz. Elbette bu, veritaban\u0131 ve I\/O y\u00fck\u00fcn\u00fc g\u00f6z ard\u0131 eden basitle\u015ftirilmi\u015f bir modeldir; ama ilk planlama i\u00e7in olduk\u00e7a faydal\u0131d\u0131r.<\/p>\n<h2><span id=\"RAM_Hesabi_PHP-FPM_Veritabani_ve_Cachein_Payini_Bolmek\">RAM Hesab\u0131: PHP-FPM, Veritaban\u0131 ve Cache\u2019in Pay\u0131n\u0131 B\u00f6lmek<\/span><\/h2>\n<p>RAM planlarken en s\u0131k yap\u0131lan hata, &#8220;8 GB RAM ald\u0131k, nas\u0131l olsa yeter&#8221; diye d\u00fc\u015f\u00fcnmek ve bu 8 GB\u2019\u0131n kimler aras\u0131nda b\u00f6l\u00fcnece\u011fini hi\u00e7 hesaplamamakt\u0131r. Oysa tipik bir WordPress\/WooCommerce veya SaaS VPS\u2019inde RAM \u015fu bile\u015fenler aras\u0131nda payla\u015f\u0131l\u0131r:<\/p>\n<ul>\n<li>\u0130\u015fletim sistemi ve temel servisler (SSH, systemd, log servisleri vb.)<\/li>\n<li>Web sunucusu + PHP-FPM veya uygulama runtime\u2019\u0131 (Node.js, Python vb.)<\/li>\n<li>Veritaban\u0131 (MySQL\/MariaDB\/PostgreSQL)<\/li>\n<li>Cache sistemleri (Redis, Memcached)<\/li>\n<li>Arka plan i\u015fler \/ queue worker\u2019lar\u0131<\/li>\n<\/ul>\n<p>Basit bir \u00f6rnek:<\/p>\n<ul>\n<li>Toplam RAM: 8 GB<\/li>\n<li>OS + temel servisler: ~1 GB<\/li>\n<li>MySQL: 2\u20133 GB (buffer pool, cache\u2019ler vs.)<\/li>\n<li>Redis: 0.5\u20131 GB<\/li>\n<li>Geriye PHP-FPM ve di\u011fer uygulamalar i\u00e7in ~3 GB kal\u0131r<\/li>\n<\/ul>\n<p>E\u011fer PHP-FPM prosesleriniz s\u0131radan bir WordPress kurulumu i\u00e7in proses ba\u015f\u0131na ortalama 50\u201380 MB RAM t\u00fcketiyorsa, 3 GB alanda teorik olarak 40\u201360 aktif PHP s\u00fcrecine yer a\u00e7abilirsiniz. Bu <strong>e\u015fzamanl\u0131 dinamik istek<\/strong> kapasitenizi do\u011frudan etkiler.<\/p>\n<p>RAM bitti\u011finde Linux \u00e7ekirde\u011fi prosesleri \u00f6ld\u00fcrmek zorunda kal\u0131r. Bu s\u0131rada hangi uygulamalar\u0131n kapanaca\u011f\u0131n\u0131 \u00f6nceden tahmin etmek zordur. OOM killer davran\u0131\u015f\u0131 ve SWAP kullan\u0131m\u0131n\u0131n detaylar\u0131 i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/vpste-ram-swap-ve-oom-killer-yonetimi\/\">RAM, SWAP ve OOM killer y\u00f6netimi rehberimizi<\/a> inceleyebilirsiniz.<\/p>\n<h2><span id=\"Kaynak_Planlamayi_Adim_Adim_Hesaplama_Pratik_Cerceve\">Kaynak Planlamay\u0131 Ad\u0131m Ad\u0131m Hesaplama: Pratik \u00c7er\u00e7eve<\/span><\/h2>\n<p>\u015eimdiye kadar farkl\u0131 senaryolar i\u00e7in &#8220;iyi ba\u015flang\u0131\u00e7&#8221; de\u011ferleri verdik. Kendi projeniz i\u00e7in daha net bir hesap yapmak isterseniz, a\u015fa\u011f\u0131daki \u00e7er\u00e7eveyi kullanabilirsiniz.<\/p>\n<h3><span id=\"1_Trafik_ve_Kullanici_Davranisini_Tahmin_Et\">1. Trafik ve Kullan\u0131c\u0131 Davran\u0131\u015f\u0131n\u0131 Tahmin Et<\/span><\/h3>\n<ul>\n<li>G\u00fcnl\u00fck beklenen ziyaret\u00e7i say\u0131s\u0131 (\u00f6rne\u011fin 5.000 ki\u015fi)<\/li>\n<li>Kullan\u0131c\u0131 ba\u015f\u0131na ortalama sayfa g\u00f6r\u00fcnt\u00fcleme (\u00f6rne\u011fin 3\u20134 sayfa)<\/li>\n<li>Yo\u011fun saatlerde olu\u015facak e\u015fzamanl\u0131 kullan\u0131c\u0131 say\u0131s\u0131 (genelde g\u00fcnl\u00fck toplam\u0131n %5\u201310\u2019u civar\u0131)<\/li>\n<\/ul>\n<p>&#8220;Yeni web sitesi i\u00e7in CPU, RAM ve trafik nas\u0131l hesaplan\u0131r&#8221; konusunu \u00f6zellikle merak ediyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/yeni-web-sitesi-icin-cpu-ram-ve-trafik-nasil-hesaplanir\/\">ayr\u0131 detayl\u0131 rehberimizi<\/a> okuyup burada anlatt\u0131klar\u0131m\u0131zla birle\u015ftirebilirsiniz.<\/p>\n<h3><span id=\"2_Sayfa_Turlerine_Gore_Dinamik_Istek_Yukunu_Belirle\">2. Sayfa T\u00fcrlerine G\u00f6re Dinamik \u0130stek Y\u00fck\u00fcn\u00fc Belirle<\/span><\/h3>\n<p>\u00d6zellikle WooCommerce ve SaaS taraf\u0131nda her sayfa e\u015fit de\u011fildir:<\/p>\n<ul>\n<li>Listeleme \/ blog yaz\u0131s\u0131 gibi cache\u2019lenebilir sayfalar<\/li>\n<li>Sepet, \u00f6deme, kullan\u0131c\u0131 hesab\u0131, panel gibi cache\u2019lenemeyen sayfalar<\/li>\n<li>A\u011f\u0131r rapor veya sorgu \u00fcreten sayfalar<\/li>\n<\/ul>\n<p>Toplam isteklerin ne kadarl\u0131k k\u0131sm\u0131n\u0131n ger\u00e7ekten PHP\/uygulama taraf\u0131ndan i\u015flendi\u011fini (cache bypass) tahmin etmek, CPU hesab\u0131n\u0131z\u0131 daha ger\u00e7ek\u00e7i yapman\u0131z\u0131 sa\u011flar. \u0130leride log analizi ile bu oranlar\u0131 net \u00f6l\u00e7mek i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/hosting-sunucu-loglarini-okumayi-ogrenin-apache-ve-nginx-ile-4xx-5xx-hatalarini-teshis-rehberi\/\">sunucu loglar\u0131n\u0131 okuma rehberi<\/a> de i\u015finize yarayacakt\u0131r.<\/p>\n<h3><span id=\"3_vCPU_Hesabi_Eszamanli_Istek_ve_Islem_Suresi\">3. vCPU Hesab\u0131: E\u015fzamanl\u0131 \u0130stek ve \u0130\u015flem S\u00fcresi<\/span><\/h3>\n<p>Basit ama i\u015fe yarayan bir yakla\u015f\u0131m:<\/p>\n<ol>\n<li>Canl\u0131ya \u00e7\u0131kmadan \u00f6nce staging ortam\u0131nda bir load test yap\u0131n (k6, JMeter, Locust vb.).<\/li>\n<li>Tipik bir dinamik iste\u011fin (\u00f6rne\u011fin \u00f6deme sayfas\u0131) ortalama CPU s\u00fcresini ve yan\u0131t s\u00fcresini \u00f6l\u00e7\u00fcn.<\/li>\n<li>Yo\u011fun zamanda bekledi\u011finiz e\u015fzamanl\u0131 dinamik istek say\u0131s\u0131n\u0131 bu de\u011ferlere b\u00f6lerek teorik CPU ihtiyac\u0131n\u0131z\u0131 \u00e7\u0131kar\u0131n.<\/li>\n<\/ol>\n<p>Bu ad\u0131mlar\u0131 daha sistematik yapmak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/trafik-patlamasindan-once-load-test-yapmak-k6-jmeter-ve-locust-ile-kapasite-olcme-rehberi\/\">trafik patlamas\u0131ndan \u00f6nce load test rehberimiz<\/a>den yararlanabilirsiniz. \u00c7\u0131kard\u0131\u011f\u0131n\u0131z sonuca %30\u201340 g\u00fcvenlik pay\u0131 eklemek, \u00fcretim ortam\u0131nda ani pikleri tolere etmenize yard\u0131mc\u0131 olur.<\/p>\n<h3><span id=\"4_RAM_Hesabi_Bilesenlere_Kota_Tanimla\">4. RAM Hesab\u0131: Bile\u015fenlere Kota Tan\u0131mla<\/span><\/h3>\n<p>Toplam RAM\u2019inizi \u015fu \u015fekilde zihninizde b\u00f6l\u00fcn:<\/p>\n<ul>\n<li>OS + temel servisler: %10\u201315<\/li>\n<li>Veritaban\u0131: %30\u201340<\/li>\n<li>Cache sistemleri: %10\u201320<\/li>\n<li>Uygulama (PHP-FPM, Node.js, worker\u2019lar): %30\u201340<\/li>\n<\/ul>\n<p>\u00d6rne\u011fin 8 GB RAM\u2019iniz varsa:<\/p>\n<ul>\n<li>~1 GB OS<\/li>\n<li>~3 GB veritaban\u0131<\/li>\n<li>~1 GB Redis<\/li>\n<li>~3 GB uygulama s\u00fcre\u00e7leri<\/li>\n<\/ul>\n<p>Daha sonra PHP-FPM veya benzeri worker\u2019lar i\u00e7in proses ba\u015f\u0131na ortalama RAM t\u00fcketimini \u00f6l\u00e7\u00fcp, ka\u00e7 e\u015fzamanl\u0131 proses a\u00e7abilece\u011finizi belirleyin. Bu say\u0131 do\u011frudan &#8220;e\u015fzamanl\u0131 dinamik istek&#8221; kapasitenizi belirler.<\/p>\n<h2><span id=\"Sik_Yapilan_Hatalar_ve_Guvenli_Pay_Birakma_Stratejisi\">S\u0131k Yap\u0131lan Hatalar ve G\u00fcvenli Pay B\u0131rakma Stratejisi<\/span><\/h2>\n<p>Kaynak planlama yaparken sahada en s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hatalar\u0131 ve nas\u0131l ka\u00e7\u0131nabilece\u011finizi k\u0131saca toparlayal\u0131m.<\/p>\n<h3><span id=\"8220Simdilik_En_Kucugu_Yeter8221_Yaklasimi\">&#8220;\u015eimdilik En K\u00fc\u00e7\u00fc\u011f\u00fc Yeter&#8221; Yakla\u015f\u0131m\u0131<\/span><\/h3>\n<p>\u00d6zellikle WooCommerce ve SaaS projelerinde, <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a>ten \u00e7ok k\u00fc\u00e7\u00fck bir VPS\u2019e ge\u00e7ip sorunlar\u0131n \u00e7\u00f6z\u00fclece\u011fini ummak yayg\u0131n bir hata. Ger\u00e7ekte ise:<\/p>\n<ul>\n<li>Payla\u015f\u0131ml\u0131 hostingte CPU ve RAM limitleri y\u00fcz\u00fcnden bo\u011fulan bir site, 1 vCPU\/1 GB VPS\u2019te de bo\u011fulur.<\/li>\n<li>Fark\u0131 yaratan \u015fey genelde sadece daha b\u00fcy\u00fck kaynak de\u011fil; do\u011fru cache, veritaban\u0131 optimizasyonu ve mimari ayr\u0131\u015fmad\u0131r.<\/li>\n<\/ul>\n<p>Payla\u015f\u0131ml\u0131 hostingten ne zaman ve nas\u0131l VPS\u2019e ge\u00e7meniz gerekti\u011fini ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/paylasimli-hostingden-vpse-sorunsuz-gecis-rehberi\/\">sorunsuz ge\u00e7i\u015f rehberi<\/a>, bu karar noktas\u0131nda \u00e7ok i\u015finize yarar.<\/p>\n<h3><span id=\"Surekli_8090_CPU_Kullanimini_8220Kaynaklar_Bosa_Gitmesin8221_Diye_Normallestirmek\">S\u00fcrekli %80\u201390 CPU Kullan\u0131m\u0131n\u0131 &#8220;Kaynaklar Bo\u015fa Gitmesin&#8221; Diye Normalle\u015ftirmek<\/span><\/h3>\n<p>CPU\u2019nun s\u00fcrekli %80\u201390 band\u0131nda olmas\u0131, sistemin her an bo\u011fulmaya haz\u0131r oldu\u011fu anlam\u0131na gelir. K\u0131sa s\u00fcreli pikler i\u00e7in sorun olmayabilir ama:<\/p>\n<ul>\n<li>Deploy, yedek alma, cron\/queue patlamalar\u0131 gibi ek y\u00fckler geldi\u011finde hemen 100%\u2019e vurur.<\/li>\n<li>Yan\u0131t s\u00fcreleri uzar, kullan\u0131c\u0131 taraf\u0131nda &#8220;site \u00e7ok yava\u015f&#8221; \u015fikayetleri ba\u015flar.<\/li>\n<\/ul>\n<p>Sa\u011fl\u0131kl\u0131 bir \u00fcretim ortam\u0131nda normal y\u00fckte %40\u201360 civar\u0131, yo\u011fun anlarda ise k\u0131sa s\u00fcreli %80\u201390 pikleri idealdir. Uzun s\u00fcreli %90+ de\u011ferler, genellikle bir \u00fcst paket veya ek node zaman\u0131n\u0131n geldi\u011fine i\u015faret eder.<\/p>\n<h3><span id=\"RAMi_Swap_ile_Telafi_Edebilecegini_Dusunmek\">RAM\u2019i Swap ile Telafi Edebilece\u011fini D\u00fc\u015f\u00fcnmek<\/span><\/h3>\n<p>Swap, RAM\u2019in &#8220;uzant\u0131s\u0131&#8221; de\u011fildir; acil durum tamponudur. \u00d6zellikle NVMe olmayan disklerde yo\u011fun Swap kullan\u0131m\u0131:<\/p>\n<ul>\n<li>Yan\u0131t s\u00fcrelerini saniyelere \u00e7\u0131kar\u0131r.<\/li>\n<li>Veritaban\u0131 ve PHP s\u00fcre\u00e7lerini s\u00fcrekli diskle konu\u015fturdu\u011fu i\u00e7in I\/O bo\u011faz\u0131na yol a\u00e7ar.<\/li>\n<\/ul>\n<p>Swap\u2019i mutlaka tan\u0131mlay\u0131n, ama &#8220;eksik RAM\u2019i swap ile kapat\u0131r\u0131m&#8221; yakla\u015f\u0131m\u0131ndan ka\u00e7\u0131n\u0131n. Y\u00fck alt\u0131nda swap kullan\u0131m\u0131n\u0131z d\u00fczenli olarak y\u00fckseliyorsa, RAM art\u0131rma veya uygulama optimizasyonu (\u00f6rne\u011fin daha az PHP-FPM havuzu, daha hafif sorgular) zaman\u0131 gelmi\u015ftir.<\/p>\n<h2><span id=\"DCHost_Uzerinde_Pratik_Planlama_Blog_WooCommerce_ve_SaaS\">DCHost \u00dczerinde Pratik Planlama: Blog, WooCommerce ve SaaS<\/span><\/h2>\n<p>Teoriyi konu\u015fmak kadar, bunu ger\u00e7ek DCHost altyap\u0131s\u0131nda nas\u0131l uygulayaca\u011f\u0131n\u0131z\u0131 da konu\u015fmak \u00f6nemli.<\/p>\n<ul>\n<li><strong>WordPress blog<\/strong>: K\u00fc\u00e7\u00fck\/orta \u00f6l\u00e7ekli projeler i\u00e7in 1\u20132 vCPU, 2\u20134 GB RAM\u2019li giri\u015f seviye VPS\u2019ler genelde fazlas\u0131yla yeterli olur. Trafi\u011finiz b\u00fcy\u00fcd\u00fck\u00e7e CPU ve RAM\u2019i kademeli art\u0131rabilirsiniz.<\/li>\n<li><strong>WooCommerce<\/strong>: En ba\u015ftan 2 vCPU, 4 GB RAM alt\u0131nda ba\u015flamaman\u0131z\u0131 tavsiye ediyoruz. B\u00fcy\u00fcd\u00fck\u00e7e veritaban\u0131n\u0131 ayr\u0131 bir VPS\u2019e ta\u015f\u0131yabilece\u011finiz mimariyi \u00f6nceden planlamak b\u00fcy\u00fck kolayl\u0131k sa\u011flar.<\/li>\n<li><strong>SaaS<\/strong>: MVP a\u015famas\u0131nda 2 vCPU, 4 GB RAM\u2019li tek VPS modeli olduk\u00e7a verimlidir. Kullan\u0131c\u0131 say\u0131s\u0131 artt\u0131k\u00e7a, veritaban\u0131 ve queue i\u015flerini ayr\u0131 VPS\u2019lere ay\u0131rmaya haz\u0131r olacak \u015fekilde tasarlamak en sa\u011fl\u0131kl\u0131 yoldur.<\/li>\n<\/ul>\n<p>DCHost olarak sadece VPS, <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> ve colocation hizmeti sunmakla kalm\u0131yor; ayn\u0131 zamanda ger\u00e7ek kullan\u0131m verilerinize bakarak <strong>somut kapasite planlama \u00f6nerileri<\/strong> de yap\u0131yoruz. Uzun vadede maliyeti d\u00fc\u015f\u00fck, performans\u0131 y\u00fcksek bir altyap\u0131 kurmak istiyorsan\u0131z, mevcut projenizin trafi\u011fi ve hedeflerini bizimle payla\u015fman\u0131z yeterli.<\/p>\n<h2><span id=\"Ozet_ve_Sonraki_Adimlar\">\u00d6zet ve Sonraki Ad\u0131mlar<\/span><\/h2>\n<p>WordPress blog, WooCommerce ma\u011faza veya SaaS \u00fcr\u00fcn\u00fc fark etmeksizin, &#8220;ka\u00e7 CPU, ne kadar RAM&#8221; sorusunun sihirli tek bir cevab\u0131 yok; ama sa\u011fl\u0131kl\u0131 bir \u00e7er\u00e7evesi var. Bu yaz\u0131da:<\/p>\n<ul>\n<li>Farkl\u0131 trafik seviyeleri i\u00e7in WordPress blog\u2019larda 1\u20134+ vCPU ve 2\u20138+ GB RAM\u2019in nerede anlaml\u0131 oldu\u011funu,<\/li>\n<li>WooCommerce i\u00e7in sipari\u015f ve kampanya y\u00fck\u00fcne g\u00f6re 2\u20138+ vCPU, 4\u201316+ GB RAM \u00f6l\u00e7eklerini,<\/li>\n<li>SaaS uygulamalar\u0131nda MVP\u2019den 100+ e\u015fzamanl\u0131 kullan\u0131c\u0131 seviyesine kadar CPU\/RAM planlamas\u0131n\u0131,<\/li>\n<li>CPU ve RAM\u2019i basit form\u00fcllerle nas\u0131l kabaca hesaplayabilece\u011finizi,<\/li>\n<li>Swap, OOM, s\u00fcrekli y\u00fcksek CPU gibi tuzaklardan nas\u0131l ka\u00e7\u0131naca\u011f\u0131n\u0131z\u0131<\/li>\n<\/ul>\n<p>\u00f6zetlemeye \u00e7al\u0131\u015ft\u0131k. Bundan sonraki ad\u0131m\u0131n\u0131z, projeniz i\u00e7in ger\u00e7ek\u00e7i trafik hedefleri koymak, basit bir kapasite hesab\u0131 yapmak ve m\u00fcmk\u00fcnse canl\u0131ya \u00e7\u0131kmadan \u00f6nce k\u00fc\u00e7\u00fck bir load test ile varsay\u0131mlar\u0131n\u0131z\u0131 test etmek olmal\u0131.<\/p>\n<p>E\u011fer &#8220;Bunlar\u0131n hepsini takip etmekle u\u011fra\u015famam, benim yerime biri baksa&#8221; diyorsan\u0131z, DCHost \u00fczerindeki VPS ve dedicated sunucu \u00e7\u00f6z\u00fcmlerimizi inceleyebilir, projenizin detaylar\u0131n\u0131 bizimle payla\u015farak birlikte en do\u011fru konfig\u00fcrasyonu tasarlayabiliriz. Do\u011fru boyutland\u0131r\u0131lm\u0131\u015f bir VPS, hem performans hem de maliyet taraf\u0131nda size uzun vadeli konfor sa\u011flar; gereksiz b\u00fcy\u00fck makinelerle b\u00fct\u00e7enizi yakmadan, k\u00fc\u00e7\u00fck makinelerle de kullan\u0131c\u0131lar\u0131n\u0131z\u0131 \u00fczmeden, tam ortas\u0131n\u0131 birlikte tutturmak m\u00fcmk\u00fcn.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Yeni bir WordPress blog, WooCommerce ma\u011faza ya da SaaS \u00fcr\u00fcn\u00fc planlarken en \u00e7ok tak\u0131lan noktalardan biri \u015fudur: &#8220;Ka\u00e7 CPU almal\u0131y\u0131m, ne kadar RAM yeter?&#8221; Proje toplant\u0131lar\u0131nda b\u00fct\u00e7e konu\u015fulurken \u00e7o\u011fu zaman tasar\u0131m, \u00f6zellik listesi ve pazarlama detayl\u0131 konu\u015fulur; altyap\u0131 taraf\u0131 ise &#8220;\u015fimdilik k\u00fc\u00e7\u00fck bir VPS al\u0131r\u0131z, b\u00fcy\u00fcrse bakar\u0131z&#8221; seviyesinde kal\u0131r. Sonra ilk kampanyada site yava\u015flar, \u00f6deme [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4339,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4338","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4338","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=4338"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4338\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4339"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4338"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4338"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4338"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}