{"id":4067,"date":"2026-01-03T16:06:30","date_gmt":"2026-01-03T13:06:30","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/cpanel-reseller-paketlerinde-limit-tasarimi-neden-bu-kadar-onemli\/"},"modified":"2026-01-03T16:06:30","modified_gmt":"2026-01-03T13:06:30","slug":"cpanel-reseller-paketlerinde-limit-tasarimi-neden-bu-kadar-onemli","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/cpanel-reseller-paketlerinde-limit-tasarimi-neden-bu-kadar-onemli\/","title":{"rendered":"cPanel reseller paketlerinde limit tasar\u0131m\u0131 neden bu kadar \u00f6nemli?"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><p>{<br \/>\n  &#8220;title&#8221;: &#8220;cPanel Reseller Paket Tasar\u0131m\u0131: CPU, inode, Disk ve E\u2011Posta Limitlerini Do\u011fru Kurgulamak&#8221;,<br \/>\n  &#8220;content&#8221;: &#8220;n<\/p>\n<p>cPanel reseller kullan\u0131rken teknik olarak elinizde k\u0131s\u0131tl\u0131 ama payla\u015f\u0131labilir bir kaynak havuzu var: CPU, RAM, disk, inode, IO, e\u2011posta kapasitesi\u2026 Bu havuzu do\u011fru b\u00f6l\u00fc\u015ft\u00fcrmedi\u011finizde iki u\u00e7 sorunla kar\u015f\u0131la\u015f\u0131rs\u0131n\u0131z: Ya agresif limitler y\u00fcz\u00fcnden m\u00fc\u015fteriler s\u00fcrekli k\u0131s\u0131tlamaya tak\u0131l\u0131r, ya da a\u015f\u0131r\u0131 esnek davran\u0131p birka\u00e7 sitenin t\u00fcm sunucuyu kilitlemesine izin verirsiniz. Her ikisi de hem markan\u0131za hem de k\u00e2rl\u0131l\u0131\u011f\u0131n\u0131za zarar verir.<\/p>\n<p>n<\/p>\n<p>DCHost taraf\u0131nda reseller altyap\u0131lar\u0131n\u0131 tasarlarken en \u00e7ok zaman harcad\u0131\u011f\u0131m\u0131z konulardan biri, bu kaynaklar\u0131n <strong>adil<\/strong>, <strong>\u00f6ng\u00f6r\u00fclebilir<\/strong> ve <strong>\u00f6l\u00e7eklenebilir<\/strong> \u015fekilde da\u011f\u0131t\u0131lmas\u0131. \u00d6zellikle ajanslar ve freelancer\u2019lar i\u00e7in, bir WordPress vitrini ile WooCommerce ma\u011fazas\u0131n\u0131n ayn\u0131 limitle \u00e7al\u0131\u015famayaca\u011f\u0131n\u0131 biliyoruz. Bu yaz\u0131da, cPanel reseller paket tasar\u0131m\u0131nda CPU, inode, disk ve e\u2011posta limitlerini nas\u0131l planlaman\u0131z gerekti\u011fini; ger\u00e7ek\u00e7i senaryolar, basit hesaplar ve pratik tavsiyelerle detayl\u0131 \u015fekilde ele alaca\u011f\u0131z.<\/p>\n<p>n<\/p>\n<p>Yaz\u0131n\u0131n oda\u011f\u0131 teknik ama dilini m\u00fcmk\u00fcn oldu\u011funca sade tutaca\u011f\u0131m. cPanel \u00fczerindeki kaynak metriklerine a\u015fina de\u011filseniz, \u00f6nce <a href=\"https:\/\/www.dchost.com\/blog\/cpanel-kaynak-limitleri-nedir-cpu-io-ram-ve-entry-processes-limitlerini-dogru-okumak\/\">cPanel kaynak limitlerini do\u011fru okuma rehberine<\/a> g\u00f6z atman\u0131z, burada anlatacaklar\u0131m\u0131z\u0131 \u00e7ok daha h\u0131zl\u0131 sindirmenizi sa\u011flar.<\/p>\n<p>nn<\/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=\"#Reseller_dunyasinda_gercekten_onemli_olan_kaynaklar\"><span class=\"toc_number toc_depth_1\">1<\/span> Reseller d\u00fcnyas\u0131nda ger\u00e7ekten \u00f6nemli olan kaynaklar<\/a><\/li><li><a href=\"#Temel_ilkeler_adalet_ongorulebilirlik_olceklenebilirlik\"><span class=\"toc_number toc_depth_1\">2<\/span> Temel ilkeler: adalet, \u00f6ng\u00f6r\u00fclebilirlik, \u00f6l\u00e7eklenebilirlik<\/a><\/li><li><a href=\"#CPU_ve_surec_Entry_Processes_limitlerini_tasarlamak\"><span class=\"toc_number toc_depth_1\">3<\/span> CPU ve s\u00fcre\u00e7 (Entry Processes) limitlerini tasarlamak<\/a><ul><li><a href=\"#1_Toplam_CPU_havuzunuzu_bilin\"><span class=\"toc_number toc_depth_2\">3.1<\/span> 1) Toplam CPU havuzunuzu bilin<\/a><\/li><li><a href=\"#2_Entry_Processes_EP_sinirlarini_dogru_ayarlayin\"><span class=\"toc_number toc_depth_2\">3.2<\/span> 2) Entry Processes (EP) s\u0131n\u0131rlar\u0131n\u0131 do\u011fru ayarlay\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#Disk_alani_ve_inode_limitlerini_dengelemek\"><span class=\"toc_number toc_depth_1\">4<\/span> Disk alan\u0131 ve inode limitlerini dengelemek<\/a><ul><li><a href=\"#1_inode_sinirlarini_paketlere_gore_bolmek\"><span class=\"toc_number toc_depth_2\">4.1<\/span> 1) inode s\u0131n\u0131rlar\u0131n\u0131 paketlere g\u00f6re b\u00f6lmek<\/a><\/li><li><a href=\"#2_Disk_alani_planlamasi_karlilik_vs_rahatlik\"><span class=\"toc_number toc_depth_2\">4.2<\/span> 2) Disk alan\u0131 planlamas\u0131: k\u00e2rl\u0131l\u0131k vs. rahatl\u0131k<\/a><\/li><li><a href=\"#3_Eposta_disk_kullanimini_unutmayin\"><span class=\"toc_number toc_depth_2\">4.3<\/span> 3) E\u2011posta disk kullan\u0131m\u0131n\u0131 unutmay\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#Eposta_limitleri_kota_saatlik_gonderim_ve_spam_riski\"><span class=\"toc_number toc_depth_1\">5<\/span> E\u2011posta limitleri: kota, saatlik g\u00f6nderim ve spam riski<\/a><ul><li><a href=\"#1_Saatlik_gonderim_limitleri\"><span class=\"toc_number toc_depth_2\">5.1<\/span> 1) Saatlik g\u00f6nderim limitleri<\/a><\/li><li><a href=\"#2_Mail_kutusu_basina_kota_plani\"><span class=\"toc_number toc_depth_2\">5.2<\/span> 2) Mail kutusu ba\u015f\u0131na kota plan\u0131<\/a><\/li><li><a href=\"#3_Spam_ve_teslim_edilebilirlik_tarafini_unutmayin\"><span class=\"toc_number toc_depth_2\">5.3<\/span> 3) Spam ve teslim edilebilirlik taraf\u0131n\u0131 unutmay\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#Ornek_senaryolar_kucuk_ajans_buyuyen_bayi_ve_kaynak_dagitimi\"><span class=\"toc_number toc_depth_1\">6<\/span> \u00d6rnek senaryolar: k\u00fc\u00e7\u00fck ajans, b\u00fcy\u00fcyen bayi ve kaynak da\u011f\u0131t\u0131m\u0131<\/a><ul><li><a href=\"#Senaryo_1_10_siteli_kucuk_ajans\"><span class=\"toc_number toc_depth_2\">6.1<\/span> Senaryo 1: 10 siteli k\u00fc\u00e7\u00fck ajans<\/a><\/li><li><a href=\"#Senaryo_2_30_siteli_buyuyen_bayi_icinde_WooCommerce_de_var\"><span class=\"toc_number toc_depth_2\">6.2<\/span> Senaryo 2: 30 siteli b\u00fcy\u00fcyen bayi (i\u00e7inde WooCommerce de var)<\/a><\/li><\/ul><\/li><li><a href=\"#Paketlendirme_stratejisi_az_sayida_net_segmentli_paket\"><span class=\"toc_number toc_depth_1\">7<\/span> Paketlendirme stratejisi: az say\u0131da, net segmentli paket<\/a><\/li><li><a href=\"#Izleme_uyari_ve_musteriye_seffaf_raporlama\"><span class=\"toc_number toc_depth_1\">8<\/span> \u0130zleme, uyar\u0131 ve m\u00fc\u015fteriye \u015feffaf raporlama<\/a><\/li><li><a href=\"#Resellerdan_ne_zaman_VPS_veya_dedicated_sunucuya_gecmelisiniz\"><span class=\"toc_number toc_depth_1\">9<\/span> Reseller\u2019dan ne zaman VPS veya dedicated sunucuya ge\u00e7melisiniz?<\/a><\/li><li><a href=\"#Sonuc_Dogru_limit_tasarimi_sizi_hem_korur_hem_buyutur\"><span class=\"toc_number toc_depth_1\">10<\/span> Sonu\u00e7: Do\u011fru limit tasar\u0131m\u0131 sizi hem korur hem b\u00fcy\u00fct\u00fcr<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Reseller_dunyasinda_gercekten_onemli_olan_kaynaklar\">Reseller d\u00fcnyas\u0131nda ger\u00e7ekten \u00f6nemli olan kaynaklar<\/span><\/h2>\n<p>n<\/p>\n<p>cPanel reseller taraf\u0131nda konu\u015ftu\u011fumuz t\u00fcm limitleri kabaca d\u00f6rt gruba ay\u0131rabiliriz:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li><strong>CPU ve s\u00fcre\u00e7 limitleri (Entry Processes, RAM, IO)<\/strong><\/li>\n<p>n  <\/p>\n<li><strong>Disk alan\u0131 ve inode<\/strong> (dosya say\u0131s\u0131)<\/li>\n<p>n  <\/p>\n<li><strong>E\u2011posta limitleri<\/strong> (hesap kotas\u0131, saatlik\/g\u00fcnl\u00fck g\u00f6nderim limiti)<\/li>\n<p>n  <\/p>\n<li><strong>Bant geni\u015fli\u011fi \/ trafik<\/strong> (bu yaz\u0131da ikincil odakta tutaca\u011f\u0131z)<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>RAM, IO ve trafik de \u00f6nemli olsa da, reseller paket tasar\u0131m\u0131nda pratikte en \u00e7ok ba\u015f\u0131n\u0131z\u0131n a\u011fr\u0131d\u0131\u011f\u0131 yerler CPU, inode, disk alan\u0131 ve e\u2011posta oluyor. \u00c7\u00fcnk\u00fc:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>CPU patlad\u0131\u011f\u0131nda siteler yava\u015fl\u0131yor veya 508\/503 hatalar\u0131 ba\u015fl\u0131yor.<\/li>\n<p>n  <\/p>\n<li>inode limitine gelindi\u011finde site dosya y\u00fckleyemiyor, eklenti g\u00fcncelleyemiyor.<\/li>\n<p>n  <\/p>\n<li>Disk alan\u0131 doldu\u011funda \u00e7o\u011fu zaman \u00f6nce e\u2011postalar g\u00f6nderilemez\/alamaz hale geliyor.<\/li>\n<p>n  <\/p>\n<li>E\u2011posta limiti yanl\u0131\u015f kurguland\u0131\u011f\u0131nda da spam \u015fik\u00e2yetleri ve IP itibar\u0131 h\u0131zla bozuluyor.<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>DCHost\u2019ta reseller altyap\u0131lar\u0131n\u0131 planlarken bu d\u00f6rt alan i\u00e7in ayr\u0131 ayr\u0131 politika belirleyip, daha sonra da ajans\/bayi profiline g\u00f6re haz\u0131r paket \u015fablonlar\u0131 \u00e7\u0131kar\u0131yoruz. Siz de benzer bir yakla\u015f\u0131m\u0131 kendi m\u00fc\u015fterilerinize sunabilirsiniz.<\/p>\n<p>nn<\/p>\n<h2><span id=\"Temel_ilkeler_adalet_ongorulebilirlik_olceklenebilirlik\">Temel ilkeler: adalet, \u00f6ng\u00f6r\u00fclebilirlik, \u00f6l\u00e7eklenebilirlik<\/span><\/h2>\n<p>n<\/p>\n<p>Limitleri tek tek konu\u015fmadan \u00f6nce, iyi tasarlanm\u0131\u015f bir cPanel reseller paketinin \u00fc\u00e7 temel \u00f6zelli\u011fini netle\u015ftirelim:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li><strong>Adalet:<\/strong> Birka\u00e7 y\u00fcksek trafikli site, geride kalan 20 k\u00fc\u00e7\u00fck vitrinin performans\u0131n\u0131 \u00f6ld\u00fcrememeli.<\/li>\n<p>n  <\/p>\n<li><strong>\u00d6ng\u00f6r\u00fclebilirlik:<\/strong> M\u00fc\u015fteri, hangi pakette ne yapabilece\u011fini <strong>tahmin edebilmeli<\/strong>. \u201cBazen \u00e7al\u0131\u015f\u0131yor, bazen k\u0131s\u0131tl\u0131yor\u201d hissi en tehlikelisidir.<\/li>\n<p>n  <\/p>\n<li><strong>\u00d6l\u00e7eklenebilirlik:<\/strong> Paket modeli; 10 site ile ba\u015flad\u0131\u011f\u0131n\u0131zda da, 100 siteye \u00e7\u0131kt\u0131\u011f\u0131n\u0131zda da mant\u0131kl\u0131 kalmal\u0131.<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Bu ilkeleri sa\u011flayabilmek i\u00e7in DCHost taraf\u0131nda \u015fu prensipleri uyguluyoruz:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>Her pakete mutlaka bir <strong>maksimum hesap say\u0131s\u0131<\/strong> tan\u0131ml\u0131yoruz (\u00f6rne\u011fin 30 cPanel hesab\u0131na kadar).<\/li>\n<p>n  <\/p>\n<li>Her cPanel hesab\u0131na <strong>minimum CPU pay\u0131<\/strong> ve <strong>minimum disk\/inode<\/strong> limiti veriyoruz.<\/li>\n<p>n  <\/p>\n<li>Ajanslarda kritik projeleri u201cPremiumu201d pakete almay\u0131 te\u015fvik ediyor, limitleri buna g\u00f6re segmentliyoruz.<\/li>\n<p>n  <\/p>\n<li>Kritik m\u00fc\u015fteriler i\u00e7in gerekti\u011finde reseller\u2019dan bir \u00fcst seviye olan <a href=\"https:\/\/www.dchost.com\/blog\/ajanslar-icin-reseller-hosting-mi-vps-mi-olceklenebilir-barindirma-stratejisi\/\">VPS tabanl\u0131 ajans mimarisine ge\u00e7i\u015f<\/a> yolunu a\u00e7\u0131k tutuyoruz.<\/li>\n<p>n<\/ul>\n<p>nn<\/p>\n<h2><span id=\"CPU_ve_surec_Entry_Processes_limitlerini_tasarlamak\">CPU ve s\u00fcre\u00e7 (Entry Processes) limitlerini tasarlamak<\/span><\/h2>\n<p>n<\/p>\n<p>CPU, pratikte m\u00fc\u015fteri memnuniyetini en \u00e7ok etkileyen metrik. \u00d6zellikle WordPress, WooCommerce, Laravel gibi PHP tabanl\u0131 sitelerde, CPU ve e\u015fzamanl\u0131 s\u00fcre\u00e7 say\u0131s\u0131 (Entry Processes) do\u011fru ayarlanmazsa \u015fu \u015fik\u00e2yetler ba\u015fl\u0131yor:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>u201cG\u00fcn i\u00e7inde belli saatlerde site \u00e7ok yava\u015fl\u0131yor.u201d<\/li>\n<p>n  <\/p>\n<li>u201cAdmin paneli s\u00fcrekli zaman a\u015f\u0131m\u0131na d\u00fc\u015f\u00fcyor.u201d<\/li>\n<p>n  <\/p>\n<li>u201cHosting panelinde CPU %100 g\u00f6r\u00fcn\u00fcyor ama neyin t\u00fcketti\u011fini anlayam\u0131yorum.u201d<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Bu semptomlarla kar\u015f\u0131la\u015f\u0131yorsan\u0131z, detayl\u0131 te\u015fhis i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/siteniz-belli-saatlerde-yavasliyorsa-paylasimli-hosting-ve-vpste-cpu-io-ve-mysql-darbogazi-teshisi\/\">CPU ve MySQL darbo\u011faz\u0131 te\u015fhis rehberine<\/a> mutlaka g\u00f6z at\u0131n. Reseller paket tasar\u0131m\u0131 yaparken kullanabilece\u011finiz pratik bir \u00e7er\u00e7eve olu\u015ftural\u0131m.<\/p>\n<p>nn<\/p>\n<h3><span id=\"1_Toplam_CPU_havuzunuzu_bilin\">1) Toplam CPU havuzunuzu bilin<\/span><\/h3>\n<p>n<\/p>\n<p>\u00d6rnek bir senaryo \u00fczerinden gidelim. Diyelim ki DCHost \u00fczerinde \u015fu \u00f6zelliklerde bir reseller plan\u0131 kullan\u0131yorsunuz:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>Toplam: 4 vCPU (payla\u015f\u0131ml\u0131 ama garanti alt s\u0131n\u0131rlar tan\u0131mlanm\u0131\u015f)<\/li>\n<p>n  <\/p>\n<li>Toplam RAM: 8 GB<\/li>\n<p>n  <\/p>\n<li>CloudLinux LVE ile her cPanel hesab\u0131na ayr\u0131 limit verilebiliyor<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Bu durumda <strong>hi\u00e7bir zaman t\u00fcm hesaplara birden 4 vCPU vaat etmemelisiniz<\/strong>. Onun yerine \u015fu mant\u0131\u011f\u0131 kullanabilirsiniz:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>Her hesap i\u00e7in <strong>minimum<\/strong> 0.5 vCPU<\/li>\n<p>n  <\/p>\n<li>Yo\u011fun siteler i\u00e7in 1 vCPUu2019ya kadar \u00e7\u0131kabilen u201cpremiumu201d paket<\/li>\n<p>n  <\/p>\n<li>Toplamda 4 vCPUu2019yu a\u015fmayacak \u015fekilde, hesap ba\u015f\u0131na CPU limitlerini payla\u015ft\u0131rmak<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>\u00d6rne\u011fin 20 hesapl\u0131k bir reseller portf\u00f6y\u00fcnde:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>15 k\u00fc\u00e7\u00fck site: 0.25 vCPU (toplam 3.75 vCPUu2019ya kadar e\u015fzamanl\u0131 tavan)<\/li>\n<p>n  <\/p>\n<li>5 orta\/yo\u011fun site: 0.75 vCPU (teorik \u00fcst s\u0131n\u0131r 3.75 vCPU)<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Ger\u00e7ekte t\u00fcm siteler ayn\u0131 anda tepeye vurmad\u0131\u011f\u0131 i\u00e7in bu, s\u00fcrd\u00fcr\u00fclebilir bir oversell oran\u0131d\u0131r. Ancak kritik nokta, <strong>premium g\u00f6rd\u00fc\u011f\u00fcn\u00fcz sitelere ger\u00e7ekten daha fazla CPU tan\u0131mlamak<\/strong>t\u0131r; herkese u201cs\u0131n\u0131rs\u0131zu201d diyerek sorunu \u00f6telemek de\u011fil.<\/p>\n<p>nn<\/p>\n<h3><span id=\"2_Entry_Processes_EP_sinirlarini_dogru_ayarlayin\">2) Entry Processes (EP) s\u0131n\u0131rlar\u0131n\u0131 do\u011fru ayarlay\u0131n<\/span><\/h3>\n<p>n<\/p>\n<p>Entry Processes, ayn\u0131 anda sunucuya gelen PHP\/CGI istek say\u0131s\u0131n\u0131n s\u0131n\u0131r\u0131d\u0131r. \u00c7ok d\u00fc\u015f\u00fck ayarlarsan\u0131z, kampanya d\u00f6neminde siteler 508 hatas\u0131 vermeye ba\u015flar; \u00e7ok y\u00fcksek ayarlarsan\u0131z da bir iki m\u00fc\u015fterinin u201cpatlama an\u0131u201d t\u00fcm sunucuyu kilitler.<\/p>\n<p>n<\/p>\n<p>DCHost taraf\u0131nda genel yakla\u015f\u0131m\u0131m\u0131z \u015f\u00f6yle:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>K\u00fc\u00e7\u00fck vitrin sitesi: 10\u201315 EP<\/li>\n<p>n  <\/p>\n<li>Kurumsal\/orta seviye WordPress: 20\u201330 EP<\/li>\n<p>n  <\/p>\n<li>K\u00fc\u00e7\u00fck WooCommerce ma\u011fazas\u0131: 30\u201340 EP<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Reseller paket \u015fablonlar\u0131n\u0131z\u0131 da buna g\u00f6re segmentleyebilirsiniz:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li><strong>Starter paket:<\/strong> 0.25 vCPU, 512\u2013768 MB RAM, 15 EP<\/li>\n<p>n  <\/p>\n<li><strong>Business paket:<\/strong> 0.5 vCPU, 1 GB RAM, 25 EP<\/li>\n<p>n  <\/p>\n<li><strong>Pro\/E\u2011ticaret paket:<\/strong> 1 vCPU, 2 GB RAM, 40 EP<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Bu s\u0131n\u0131rlar, \u00f6zellikle WordPress a\u011f\u0131rl\u0131kl\u0131 reseller portf\u00f6ylerinde olduk\u00e7a sa\u011fl\u0131kl\u0131 \u00e7al\u0131\u015f\u0131yor. CPU\/EP taraf\u0131n\u0131 daha derin anlamak isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/cpanelde-kaynak-limitleri-cpu-io-ep-ram-ve-resource-limit-reached-hatasi\/\">cPanel kaynak limitleri ve &#8220;Resource Limit Reached&#8221; yaz\u0131m\u0131zdaki grafiklere<\/a> mutlaka bak\u0131n.<\/p>\n<p>nn<\/p>\n<h2><span id=\"Disk_alani_ve_inode_limitlerini_dengelemek\">Disk alan\u0131 ve inode limitlerini dengelemek<\/span><\/h2>\n<p>n<\/p>\n<p>Disk alan\u0131n\u0131 herkes konu\u015fur ama <strong>inode<\/strong> (dosya say\u0131s\u0131) \u00e7o\u011fu zaman g\u00f6zden ka\u00e7\u0131r\u0131l\u0131r. Oysa \u00e7ok say\u0131da k\u00fc\u00e7\u00fck dosyadan olu\u015fan bir site, diskte g\u00f6rece az yer kaplasa bile inode limitine \u00e7ok h\u0131zl\u0131 vurabilir.<\/p>\n<p>n<\/p>\n<p>inode kabaca u201cka\u00e7 adet dosya ve klas\u00f6r\u00fcn\u00fcz var?u201d sorusunun cevab\u0131d\u0131r. WordPress \u00e7ekirde\u011fi + eklentiler + temalar + cache dosyalar\u0131 derken, tek bir sitede 80\u2013120 bin inode g\u00f6rmek hi\u00e7 \u015fa\u015f\u0131rt\u0131c\u0131 de\u011fildir. \u00dczerine bir de e\u2011posta klas\u00f6rleri eklenince, s\u0131n\u0131rlar h\u0131zla dolmaya ba\u015flar.<\/p>\n<p>nn<\/p>\n<h3><span id=\"1_inode_sinirlarini_paketlere_gore_bolmek\">1) inode s\u0131n\u0131rlar\u0131n\u0131 paketlere g\u00f6re b\u00f6lmek<\/span><\/h3>\n<p>n<\/p>\n<p>\u00d6rnek olarak 1 milyon inode havuzuna sahip bir reseller d\u00fc\u015f\u00fcnelim. Bunu da\u011f\u0131t\u0131rken \u015fu modeli kullanabilirsiniz:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li><strong>Starter paket:<\/strong> 50.000 inode<\/li>\n<p>n  <\/p>\n<li><strong>Business paket:<\/strong> 100.000 inode<\/li>\n<p>n  <\/p>\n<li><strong>Pro paket:<\/strong> 200.000 inode<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>20 m\u00fc\u015fterinizin 10u2019u Starter, 7u2019si Business, 3u2019\u00fc Pro olsa teorik \u00fcst s\u0131n\u0131r 1.6 milyon inode olur; ancak hepsi s\u0131n\u0131r\u0131na vurmaz. Yine de <strong>\u00f6zellikle yedek dizinleri, eski staging kopyalar\u0131 ve gereksiz cache klas\u00f6rleri<\/strong> sebebiyle inode \u015fi\u015fmesinin \u00e7ok yayg\u0131n oldu\u011funu unutmay\u0131n.<\/p>\n<p>n<\/p>\n<p>M\u00fc\u015fterilerinizi e\u011fitmek i\u00e7in onlara <a href=\"https:\/\/www.dchost.com\/blog\/paylasimli-hostingde-inode-limitine-takilmamak-icin-uygulamali-temizlik-rehberi\/\">inode limitine tak\u0131lmamak i\u00e7in uygulamal\u0131 temizlik rehberimizi<\/a> g\u00f6ndermek, destek y\u00fck\u00fcn\u00fcz\u00fc ciddi anlamda azaltacakt\u0131r.<\/p>\n<p>nn<\/p>\n<h3><span id=\"2_Disk_alani_planlamasi_karlilik_vs_rahatlik\">2) Disk alan\u0131 planlamas\u0131: k\u00e2rl\u0131l\u0131k vs. rahatl\u0131k<\/span><\/h3>\n<p>n<\/p>\n<p>Disk taraf\u0131nda iki parametreyi ayn\u0131 anda d\u00fc\u015f\u00fcnmelisiniz:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>TB ba\u015f\u0131na maliyetiniz (NVMe\/SATA, replikasyon, yedekleme politikalar\u0131)<\/li>\n<p>n  <\/p>\n<li>M\u00fc\u015fterilerin tipik kullan\u0131m al\u0131\u015fkanl\u0131klar\u0131 (WordPress + mail, e\u2011ticaret, dosya payla\u015f\u0131m\u0131 vb.)<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>DCHost taraf\u0131nda g\u00f6zlemimiz \u015fu y\u00f6nde:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>Sadece web sitesi (vitrin, blog): 1\u20133 GB aras\u0131 rahat yeter.<\/li>\n<p>n  <\/p>\n<li>Web sitesi + hafif e\u2011posta kullan\u0131m\u0131: 5\u201310 GB aras\u0131.<\/li>\n<p>n  <\/p>\n<li>WooCommerce \/ katalog + d\u00fczenli e\u2011posta: 10\u201320 GB aras\u0131.<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Bu verilerle birlikte, reseller paketlerinizi \u015f\u00f6yle tasarlayabilirsiniz:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li><strong>Starter:<\/strong> 2\u20133 GB disk, 50.000 inode<\/li>\n<p>n  <\/p>\n<li><strong>Business:<\/strong> 5\u201310 GB disk, 100.000 inode<\/li>\n<p>n  <\/p>\n<li><strong>Pro:<\/strong> 15\u201325 GB disk, 200.000 inode<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>\u00d6zellikle WooCommerce ve b\u00fcy\u00fck medya ar\u015fivli sitelerde, daha yay\u0131mlamadan \u00f6nce disk\/i\u00e7erik beklentisini konu\u015fup <a href=\"https:\/\/www.dchost.com\/blog\/woocommerce-ve-buyuk-wordpress-siteleri-icin-disk-iops-ve-inode-planlama-rehberi\/\">disk ve inode planlama rehberimizdeki tablolara<\/a> g\u00f6re yol \u00e7izmek, sizi sonradan ya\u015fanacak tats\u0131z s\u00fcrprizlerden korur.<\/p>\n<p>nn<\/p>\n<h3><span id=\"3_Eposta_disk_kullanimini_unutmayin\">3) E\u2011posta disk kullan\u0131m\u0131n\u0131 unutmay\u0131n<\/span><\/h3>\n<p>n<\/p>\n<p>Ger\u00e7ekte disk t\u00fcketiminin \u00f6nemli k\u0131sm\u0131n\u0131 bazen web sitesi de\u011fil, e\u2011postalar yapar. 10\u201315 ki\u015filik bir \u015firket, ar\u015fiv temizli\u011fi yap\u0131lmad\u0131\u011f\u0131nda rahatl\u0131kla 20\u201330 GB e\u2011posta kotas\u0131n\u0131 doldurabilir. Bu nedenle:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>Web sitesi disk kotas\u0131 ile e\u2011posta kotas\u0131n\u0131 <strong>ayn\u0131 havuzdan yedi\u011fini<\/strong> m\u00fc\u015fteriye iyi anlat\u0131n.<\/li>\n<p>n  <\/p>\n<li>cPanel i\u00e7inde mail kotas\u0131 uyar\u0131lar\u0131n\u0131 aktif edin.<\/li>\n<p>n  <\/p>\n<li>M\u00fc\u015fterilerinize d\u00fczenli ar\u015fiv\/temizlik i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/cpanelde-e-posta-alani-yonetimi-kota-ek-temizligi-ve-dev-mail-kutularini-kucultme-rehberi\/\">cPanel e\u2011posta alan\u0131 y\u00f6netimi rehberimizi<\/a> g\u00f6nderin.<\/li>\n<p>n<\/ul>\n<p>nn<\/p>\n<h2><span id=\"Eposta_limitleri_kota_saatlik_gonderim_ve_spam_riski\">E\u2011posta limitleri: kota, saatlik g\u00f6nderim ve spam riski<\/span><\/h2>\n<p>n<\/p>\n<p>Reseller paketlerinde en hassas konu genelde e\u2011postad\u0131r. \u00c7\u00fcnk\u00fc:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>Spam yapan <strong>tek bir m\u00fc\u015fteri<\/strong>, t\u00fcm IP itibar\u0131n\u0131z\u0131 riske atabilir.<\/li>\n<p>n  <\/p>\n<li>Yetersiz limitler ise b\u00fclten g\u00f6nderen m\u00fc\u015fterilerinizi mutsuz eder.<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>DCHost taraf\u0131nda izledi\u011fimiz yakla\u015f\u0131m\u0131 biraz basitle\u015ftirerek payla\u015fay\u0131m; siz onu kendi i\u015f modelinize g\u00f6re daralt\u0131p\/geni\u015fletebilirsiniz.<\/p>\n<p>nn<\/p>\n<h3><span id=\"1_Saatlik_gonderim_limitleri\">1) Saatlik g\u00f6nderim limitleri<\/span><\/h3>\n<p>n<\/p>\n<p>cPanel\/Exim taraf\u0131nda hesap bazl\u0131 saatlik g\u00f6nderim limiti tan\u0131mlamak, spam riskini ciddi \u00f6l\u00e7\u00fcde azalt\u0131r. \u00d6neri aral\u0131klar:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li><strong>Standart kurumsal site:<\/strong> 100\u2013200 mail\/saat<\/li>\n<p>n  <\/p>\n<li><strong>K\u00fc\u00e7\u00fck b\u00fclten g\u00f6nderen m\u00fc\u015fteri:<\/strong> 300\u2013500 mail\/saat<\/li>\n<p>n  <\/p>\n<li><strong>Yo\u011fun pazarlama yapan, liste onayl\u0131 m\u00fc\u015fteri:<\/strong> 800\u20131000 mail\/saat (m\u00fcmk\u00fcnse ayr\u0131 IP veya ayr\u0131 altyap\u0131)<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Reseller paketlerinde u201cStarteru201d m\u00fc\u015fterilere 100\u2013200, u201cBusinessu201d m\u00fc\u015fterilere 300\u2013500, u201cProu201d m\u00fc\u015fterilere 800 civar\u0131 \u00fcst s\u0131n\u0131r tan\u0131mlamak, hem IP itibar\u0131n\u0131 korur hem de i\u015f yapan m\u00fc\u015fterilerin elini kolunu ba\u011flamaz.<\/p>\n<p>nn<\/p>\n<h3><span id=\"2_Mail_kutusu_basina_kota_plani\">2) Mail kutusu ba\u015f\u0131na kota plan\u0131<\/span><\/h3>\n<p>n<\/p>\n<p>Mail hesab\u0131 ba\u015f\u0131na kota verirken, web disk havuzunuzla \u00e7arp\u0131\u015fmayacak mant\u0131kl\u0131 rakamlar se\u00e7in:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>K\u00fc\u00e7\u00fck ekipler: Ki\u015fi ba\u015f\u0131 1\u20132 GB<\/li>\n<p>n  <\/p>\n<li>Orta boy \u015firket: Ki\u015fi ba\u015f\u0131 2\u20135 GB<\/li>\n<p>n  <\/p>\n<li>A\u011f\u0131r ar\u015fivci m\u00fc\u015fteriler: 10 GB ve \u00fczeri (veya harici ar\u015fiv \u00e7\u00f6z\u00fcmleri)<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Burada kilit nokta, <strong>kalabal\u0131k ekipli m\u00fc\u015fterileri Pro pakete ta\u015f\u0131mak<\/strong>. 50 ki\u015filik bir ekibin her birine 5 GB verdi\u011finizde, tek m\u00fc\u015fteri 250 GB t\u00fcketecektir; bu genellikle reseller mimarisinin \u00fcst\u00fcne \u00e7\u0131kar ve ayr\u0131 \u00e7\u00f6z\u00fcmleri (<a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a>, dedicated, ayr\u0131 e\u2011posta altyap\u0131s\u0131) konu\u015fmak gerekir.<\/p>\n<p>nn<\/p>\n<h3><span id=\"3_Spam_ve_teslim_edilebilirlik_tarafini_unutmayin\">3) Spam ve teslim edilebilirlik taraf\u0131n\u0131 unutmay\u0131n<\/span><\/h3>\n<p>n<\/p>\n<p>Limit tasar\u0131m\u0131 sadece rakamlardan ibaret de\u011fil. SPF, DKIM, DMARC, rDNS gibi kay\u0131tlar\u0131n do\u011fru kurulmas\u0131, spam riskini azalt\u0131r ve teslim edilebilirli\u011fi art\u0131r\u0131r. Bu konuda ad\u0131m ad\u0131m bir kurulum yapmak isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/spf-dkim-ve-dmarc-nedir-ozel-alan-adi-ile-e-posta-dogrulamasini-cpanel-ve-vpste-sifirdan-kurmak\/\">SPF, DKIM ve DMARC rehberimizi<\/a> temel check\u2011list olarak kullanabilirsiniz.<\/p>\n<p>nn<\/p>\n<h2><span id=\"Ornek_senaryolar_kucuk_ajans_buyuyen_bayi_ve_kaynak_dagitimi\">\u00d6rnek senaryolar: k\u00fc\u00e7\u00fck ajans, b\u00fcy\u00fcyen bayi ve kaynak da\u011f\u0131t\u0131m\u0131<\/span><\/h2>\n<p>n<\/p>\n<p>Teoriyi biraz somutla\u015ft\u0131ral\u0131m. DCHost \u00fczerinde a\u015fa\u011f\u0131daki gibi bir reseller altyap\u0131n\u0131z oldu\u011funu varsayal\u0131m:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>4 vCPU, 8 GB RAM<\/li>\n<p>n  <\/p>\n<li>200 GB NVMe disk<\/li>\n<p>n  <\/p>\n<li>1 milyon inode<\/li>\n<p>n<\/ul>\n<p>nn<\/p>\n<h3><span id=\"Senaryo_1_10_siteli_kucuk_ajans\">Senaryo 1: 10 siteli k\u00fc\u00e7\u00fck ajans<\/span><\/h3>\n<p>n<\/p>\n<p>Ajans\u0131n\u0131zda 10 m\u00fc\u015fteri var; hepsi WordPress tabanl\u0131, WooCommerce yok. \u00c7o\u011fu kurumsal vitrinden olu\u015fuyor.<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>8 siteyi <strong>Business paket<\/strong>e, 2 siteyi <strong>Starter<\/strong>a alabilirsiniz.<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>\u00d6nerilen kaynak da\u011f\u0131l\u0131m\u0131:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>Starter (2 site): 0.25 vCPU, 512 MB RAM, 15 EP, 3 GB disk, 50.000 inode<\/li>\n<p>n  <\/p>\n<li>Business (8 site): 0.5 vCPU, 1 GB RAM, 25 EP, 5 GB disk, 100.000 inode<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Teorik toplam:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>CPU: 2 \u00d7 0.25 + 8 \u00d7 0.5 = 4.5 vCPU (oversell var ama pratikte ayn\u0131 anda tavan yapmazlar)<\/li>\n<p>n  <\/p>\n<li>Disk: 2 \u00d7 3 + 8 \u00d7 5 = 46 GB<\/li>\n<p>n  <\/p>\n<li>inode: 2 \u00d7 50.000 + 8 \u00d7 100.000 = 900.000 inode<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Bu portf\u00f6yde as\u0131l risk inode taraf\u0131nda; 1 milyonluk havuzun %90u2019\u0131n\u0131 t\u00fckettiniz. Burada iki tedbir i\u015fe yarar:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>\u0130lk g\u00fcnden itibaren m\u00fc\u015fteriye d\u00fczenli temizlik ve ar\u015fiv politikas\u0131n\u0131 anlatmak.<\/li>\n<p>n  <\/p>\n<li>Staging kopyalar\u0131, eski yedek dosyalar\u0131n\u0131 ayn\u0131 hosting i\u00e7inde tutmak yerine harici yedeklere ta\u015f\u0131mak.<\/li>\n<p>n<\/ul>\n<p>nn<\/p>\n<h3><span id=\"Senaryo_2_30_siteli_buyuyen_bayi_icinde_WooCommerce_de_var\">Senaryo 2: 30 siteli b\u00fcy\u00fcyen bayi (i\u00e7inde WooCommerce de var)<\/span><\/h3>\n<p>n<\/p>\n<p>Bu kez 30 cPanel hesab\u0131 y\u00f6neten daha b\u00fcy\u00fck bir reseller d\u00fc\u015f\u00fcnelim. M\u00fc\u015fteri k\u0131r\u0131l\u0131m\u0131 \u015f\u00f6yle olsun:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>15 k\u00fc\u00e7\u00fck vitrin\/blog<\/li>\n<p>n  <\/p>\n<li>10 kurumsal site (orta trafik)<\/li>\n<p>n  <\/p>\n<li>5 WooCommerce \/ katalog sitesi<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Bu tabloya \u015f\u00f6yle yakla\u015fabilirsiniz:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>15 k\u00fc\u00e7\u00fck site \u2192 Starter<\/li>\n<p>n  <\/p>\n<li>10 kurumsal site \u2192 Business<\/li>\n<p>n  <\/p>\n<li>5 WooCommerce \u2192 Pro<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Kaynak da\u011f\u0131l\u0131m\u0131 (\u00f6neri):<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li><strong>Starter:<\/strong> 0.25 vCPU, 512 MB RAM, 15 EP, 2 GB disk, 40.000 inode<\/li>\n<p>n  <\/p>\n<li><strong>Business:<\/strong> 0.5 vCPU, 1 GB RAM, 25 EP, 5 GB disk, 80.000 inode<\/li>\n<p>n  <\/p>\n<li><strong>Pro:<\/strong> 1 vCPU, 2 GB RAM, 40 EP, 20 GB disk, 200.000 inode<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Teorik toplama bakal\u0131m:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>CPU: 15 \u00d7 0.25 + 10 \u00d7 0.5 + 5 \u00d7 1 = 3.75 + 5 + 5 = 13.75 vCPU<\/li>\n<p>n  <\/p>\n<li>Disk: 15 \u00d7 2 + 10 \u00d7 5 + 5 \u00d7 20 = 30 + 50 + 100 = 180 GB<\/li>\n<p>n  <\/p>\n<li>inode: 15 \u00d7 40.000 + 10 \u00d7 80.000 + 5 \u00d7 200.000 = 600.000 + 800.000 + 1.000.000 = 2.4 milyon<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Burada iki \u015feyi fark etmi\u015f olmal\u0131s\u0131n\u0131z:<\/p>\n<p>n<\/p>\n<ol>n  <\/p>\n<li>CPU taraf\u0131nda olduk\u00e7a ciddi bir oversell var (4 vCPU havuza kar\u015f\u0131 13.75 vCPU teorik). Fakat t\u00fcm sitelerin ayn\u0131 anda tepeye vurma ihtimali d\u00fc\u015f\u00fck oldu\u011fu i\u00e7in, iyi \u00f6nbellekleme (cache), CDN ve optimizasyon ile bu senaryo <strong>makul seviyede<\/strong> \u00e7al\u0131\u015fabilir.<\/li>\n<p>n  <\/p>\n<li>inode ve disk taraf\u0131nda mevcut havuzunuzu a\u015ft\u0131n\u0131z; bu da ya daha b\u00fcy\u00fck bir reseller plan\u0131na, ya da par\u00e7ay\u0131 VPS\/dedicated tarafa kayd\u0131rmaya i\u015faret ediyor.<\/li>\n<p>n<\/ol>\n<p>n<\/p>\n<p>Tam bu noktada, u201cBu kadar siteyi h\u00e2l\u00e2 reseller \u00fczerinde mi tutmal\u0131y\u0131m, yoksa art\u0131k <a href=\"https:\/\/www.dchost.com\/blog\/reseller-hosting-mi-vps-mi-ajans-ve-freelancerlar-icin-yol-haritasi\/\">VPS tabanl\u0131 ajans mimarisine ge\u00e7menin zaman\u0131 m\u0131?<\/a>u201d sorusu g\u00fcndeme gelir. DCHost olarak genellikle \u015fu e\u015fikleri referans al\u0131yoruz:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>Toplam 30\u201340 siteyi ge\u00e7tiyseniz,<\/li>\n<p>n  <\/p>\n<li>\u0130\u00e7lerinde trafik yo\u011fun birka\u00e7 WooCommerce \/ kampanya sitesi varsa,<\/li>\n<p>n  <\/p>\n<li>inode ve disk planlamas\u0131 s\u00fcrekli u201ck\u0131rm\u0131z\u0131 alandau201d dola\u015f\u0131yorsa,<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Art\u0131k y\u00f6netilen bir VPS veya dedicated \u00e7\u00f6z\u00fcm\u00fc d\u00fc\u015f\u00fcnmenin zaman\u0131 gelmi\u015f demektir.<\/p>\n<p>nn<\/p>\n<h2><span id=\"Paketlendirme_stratejisi_az_sayida_net_segmentli_paket\">Paketlendirme stratejisi: az say\u0131da, net segmentli paket<\/span><\/h2>\n<p>n<\/p>\n<p>Reseller m\u00fc\u015fterilerinize sunaca\u011f\u0131n\u0131z alt paketleri tasarlarken, en yayg\u0131n hata 7\u20138 farkl\u0131 paket \u00e7\u0131karmak oluyor. Sonu\u00e7: Hem siz hem de m\u00fc\u015fteri kafas\u0131 kar\u0131\u015f\u0131k bir fiyat tablosu ile ba\u015f ba\u015fa kal\u0131yorsunuz. DCHostu2019ta g\u00f6rd\u00fc\u011f\u00fcm\u00fcz en sa\u011fl\u0131kl\u0131 model, <strong>3 veya en fazla 4 segmentli<\/strong> yap\u0131:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>Basic\/Starter (k\u00fc\u00e7\u00fck vitrin, ki\u015fisel bloglar)<\/li>\n<p>n  <\/p>\n<li>Business (kurumsal siteler, hafif formlar)<\/li>\n<p>n  <\/p>\n<li>Pro\/E\u2011ticaret (WooCommerce, LMS, \u00fcyelik siteleri)<\/li>\n<p>n  <\/p>\n<li>(\u0130ste\u011fe ba\u011fl\u0131) \u00d6zel\/Enterprise (tamamen case bazl\u0131, genelde art\u0131k VPS\/dedicated taraf\u0131)<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Her paket i\u00e7in mutlaka tan\u0131mlay\u0131n:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>Kullan\u0131c\u0131 ba\u015f\u0131na minimum CPU, RAM, EP<\/li>\n<p>n  <\/p>\n<li>Disk ve inode limiti<\/li>\n<p>n  <\/p>\n<li>Mail kutusu say\u0131s\u0131 ve toplam mail kotas\u0131<\/li>\n<p>n  <\/p>\n<li>Saatlik g\u00f6nderim limiti<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Bunlar\u0131 s\u00f6zle\u015fme ve fiyatland\u0131rma sayfalar\u0131nda net \u015fekilde yazmak, ileride \u00e7\u0131kabilecek \u00e7o\u011fu tart\u0131\u015fmay\u0131 en ba\u015ftan engeller. Paket tasar\u0131m\u0131 ve limit y\u00f6netimi konusunda daha geni\u015f bir \u00e7er\u00e7eve isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/reseller-hosting-yonetimi-rehberi-paketler-limitler-ve-izolasyon\/\">Reseller hosting y\u00f6netimi rehberimiz<\/a> sizin i\u00e7in iyi bir tamamlay\u0131c\u0131 olacakt\u0131r.<\/p>\n<p>nn<\/p>\n<h2><span id=\"Izleme_uyari_ve_musteriye_seffaf_raporlama\">\u0130zleme, uyar\u0131 ve m\u00fc\u015fteriye \u015feffaf raporlama<\/span><\/h2>\n<p>n<\/p>\n<p>\u0130yi tasarlanm\u0131\u015f limitler kadar, <strong>iyi izleme ve \u015feffaf raporlama<\/strong> da \u00f6nemli. Aksi halde m\u00fc\u015fteri, u201cKaynak limitine tak\u0131ld\u0131mu201d c\u00fcmlesini her duydu\u011funda bunun bir bahane oldu\u011funu d\u00fc\u015f\u00fcnebilir.<\/p>\n<p>n<\/p>\n<p>\u00d6nerdi\u011fimiz pratikler:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>cPanel istatistik ekran\u0131n\u0131 m\u00fc\u015fteriye nas\u0131l okuyaca\u011f\u0131n\u0131 g\u00f6steren k\u0131sa bir dok\u00fcman haz\u0131rlay\u0131n.<\/li>\n<p>n  <\/p>\n<li>CPU\/EP tavan yapt\u0131\u011f\u0131 anlarda DCHost taraf\u0131nda tuttu\u011funuz grafiklerden ekran g\u00f6r\u00fcnt\u00fcs\u00fc al\u0131p m\u00fc\u015fteriye a\u00e7\u0131klamayla g\u00f6nderin.<\/li>\n<p>n  <\/p>\n<li>inode ve disk kullan\u0131m\u0131 %80u2019i ge\u00e7ti\u011finde, otomatik uyar\u0131 maili atan bir izleme kurgulay\u0131n.<\/li>\n<p>n  <\/p>\n<li>Kritik siteler i\u00e7in ayl\u0131k u201cKaynak Kullan\u0131m \u00d6zetiu201d raporu, ajanslar a\u00e7\u0131s\u0131ndan ciddi katma de\u011fer yarat\u0131r.<\/li>\n<p>n<\/ul>\n<p>nn<\/p>\n<h2><span id=\"Resellerdan_ne_zaman_VPS_veya_dedicated_sunucuya_gecmelisiniz\">Reseller\u2019dan ne zaman VPS veya <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a>ya ge\u00e7melisiniz?<\/span><\/h2>\n<p>n<\/p>\n<p>Reseller \u00e7ok verimlidir; \u00f6zellikle 5\u201330 site aras\u0131 portf\u00f6y\u00fc olan ajanslar i\u00e7in ideal. Ancak belli bir \u00f6l\u00e7e\u011fin \u00fczerine \u00e7\u0131kt\u0131\u011f\u0131n\u0131zda, reseller yap\u0131n\u0131n do\u011fas\u0131 gere\u011fi baz\u0131 duvarlara toslars\u0131n\u0131z:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>Toplam inode ve disk havuzu s\u00fcrekli t\u0131kan\u0131yorsa,<\/li>\n<p>n  <\/p>\n<li>CPU\/EP taraf\u0131nda birka\u00e7 site t\u00fcm portf\u00f6y\u00fc etkiliyorsa,<\/li>\n<p>n  <\/p>\n<li>M\u00fc\u015fterilerinizin bir k\u0131sm\u0131 \u00f6zel PHP eklentileri, Node.js uygulamalar\u0131, background i\u015fler talep ediyorsa,<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>Art\u0131k kendi VPS veya dedicated sunucunuza ge\u00e7mek genelde daha mant\u0131kl\u0131 hale gelir. DCHost taraf\u0131nda pek \u00e7ok ajans, \u00f6nce reseller ile ba\u015fl\u0131yor; sonras\u0131nda i\u015f b\u00fcy\u00fcd\u00fck\u00e7e y\u00f6netilen VPS, ileride de dedicated veya colocation mimarisine ilerliyor. Tam bu ge\u00e7i\u015f noktas\u0131n\u0131 daha net g\u00f6rmek i\u00e7in, <a href=\"https:\/\/www.dchost.com\/blog\/ajanslar-icin-reseller-hosting-mi-vps-mi-olceklenebilir-barindirma-stratejisi\/\">ajanslar i\u00e7in reseller m\u0131 VPS mi rehberimizi<\/a> mutlaka okuman\u0131z\u0131 \u00f6neririm.<\/p>\n<p>nn<\/p>\n<h2><span id=\"Sonuc_Dogru_limit_tasarimi_sizi_hem_korur_hem_buyutur\">Sonu\u00e7: Do\u011fru limit tasar\u0131m\u0131 sizi hem korur hem b\u00fcy\u00fct\u00fcr<\/span><\/h2>\n<p>n<\/p>\n<p>cPanel reseller paket tasar\u0131m\u0131, sadece u201cka\u00e7 GB verelim, ka\u00e7 site host edilsinu201d sorusundan ibaret de\u011fil. CPU, inode, disk ve e\u2011posta limitlerini bilin\u00e7li kurgulad\u0131\u011f\u0131n\u0131zda:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>Bir m\u00fc\u015fteri di\u011ferlerini ezmeden, t\u00fcm portf\u00f6y kararl\u0131 \u00e7al\u0131\u015f\u0131r.<\/li>\n<p>n  <\/p>\n<li>Beklenmedik kaynak patlamalar\u0131nda sorunu h\u0131zl\u0131 te\u015fhis edip do\u011fru pakete y\u00f6nlendirebilirsiniz.<\/li>\n<p>n  <\/p>\n<li>Kendi maliyetinizi (disk, IOPS, CPU, IP, yedekleme) kontrol alt\u0131nda tutarak k\u00e2rl\u0131 kal\u0131rs\u0131n\u0131z.<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>DCHost olarak bizim g\u00f6rd\u00fc\u011f\u00fcm\u00fcz en ba\u015far\u0131l\u0131 ajans ve bayiler, ba\u015ftan itibaren net limit politikas\u0131 koyan ve bunu m\u00fc\u015fterileriyle \u015feffaf payla\u015fanlar. Siz de reseller i\u015finizi bir \u00fcst seviyeye ta\u015f\u0131mak istiyorsan\u0131z, \u00f6nce mevcut portf\u00f6y\u00fcn\u00fcz\u00fc analiz edip:<\/p>\n<p>n<\/p>\n<ul>n  <\/p>\n<li>Ka\u00e7 siteniz var, hangi profilde?<\/li>\n<p>n  <\/p>\n<li>Hangi siteler yo\u011fun CPU\/IO kullan\u0131yor?<\/li>\n<p>n  <\/p>\n<li>inode ve disk taraf\u0131nda kimler k\u0131rm\u0131z\u0131 alanda?<\/li>\n<p>n  <\/p>\n<li>E\u2011posta taraf\u0131nda kimler saatlik limite yakla\u015fm\u0131\u015f durumda?<\/li>\n<p>n<\/ul>\n<p>n<\/p>\n<p>gibi sorulara net cevaplar \u00e7\u0131kar\u0131n. Ard\u0131ndan bu yaz\u0131daki segmentasyon \u00f6rneklerini kendinize uyarlayarak 3\u20134 net paket olu\u015fturun. E\u011fer u201cReseller art\u0131k beni zorluyor, kendi sunucuma ge\u00e7mek istiyorumu201d noktas\u0131ndaysan\u0131z, DCHost \u00fczerinde y\u00f6netilen VPS, dedicated ve colocation se\u00e7eneklerimizle ayn\u0131 yakla\u015f\u0131m\u0131 daha esnek bir altyap\u0131ya ta\u015f\u0131yabilirsiniz.<\/p>\n<p>n<\/p>\n<p>Do\u011fru tasarlanm\u0131\u015f bir cPanel reseller yap\u0131s\u0131, hem m\u00fc\u015fterilerinizin web sitelerini g\u00fcvenle bar\u0131nd\u0131rman\u0131z\u0131 sa\u011flar hem de size s\u00fcrd\u00fcr\u00fclebilir bir hosting i\u015f modeli sunar. Ad\u0131m ad\u0131m ilerleyin, \u00f6l\u00e7\u00fcn, iyile\u015ftirin ve limitleri k\u00e2\u011f\u0131t \u00fczerinde de\u011fil ger\u00e7ek kullan\u0131m verisine g\u00f6re g\u00fcncel tutun.<\/p>\n<p>n&#8221;,<br \/>\n  &#8220;focus_keyword&#8221;: &#8220;cPanel reseller paket tasar\u0131m\u0131&#8221;,<br \/>\n  &#8220;meta_description&#8221;: &#8220;cPanel reseller paket tasar\u0131m\u0131 i\u00e7in CPU, inode, disk ve e\u2011posta limitlerini nas\u0131l belirleyece\u011finizi ad\u0131m ad\u0131m anlat\u0131yoruz. Ajans ve bayiler i\u00e7in pratik rehber.&#8221;,<br \/>\n  &#8220;faqs&#8221;: [<br \/>\n    {<br \/>\n      &#8220;question&#8221;: &#8220;cPanel reseller paketinde overselling yapmak g\u00fcvenli mi?&#8221;,<br \/>\n      &#8220;answer&#8221;: &#8220;Tamamen u201cs\u0131f\u0131r oversellu201d \u00e7ok g\u00fcvenli ama ticari olarak verimsizdir; agresif oversell ise birka\u00e7 m\u00fc\u015fterinin t\u00fcm altyap\u0131y\u0131 \u00e7\u00f6kertmesine yol a\u00e7abilir. Sa\u011fl\u0131kl\u0131 olan, CPU ve IO taraf\u0131nda kontroll\u00fc oversell, disk ve inode taraf\u0131nda ise daha muhafazak\u00e2r bir yakla\u015f\u0131m uygulamakt\u0131r. \u00d6rne\u011fin 4 vCPU havuzuna teorik olarak 8\u201310 vCPU edecek limit tan\u0131mlamak genelde y\u00f6netilebilir; ancak disk ve inodeu201da fiziksel s\u0131n\u0131r\u0131 a\u015fmayacak \u015fekilde plan yapmal\u0131s\u0131n\u0131z. Anahtar nokta, iyi \u00f6nbellekleme, izleme ve limit a\u015f\u0131mlar\u0131nda h\u0131zl\u0131 aksiyon almak; yani oversell oran\u0131n\u0131z\u0131 ger\u00e7ek kullan\u0131m verisine bakarak s\u00fcrekli ayarlamakt\u0131r.&#8221;<br \/>\n    },<br \/>\n    {<br \/>\n      &#8220;question&#8221;: &#8220;Reseller m\u00fc\u015fterilerim i\u00e7in inode limitini ka\u00e7ta tutmal\u0131y\u0131m?&#8221;,<br \/>\n      &#8220;answer&#8221;: &#8220;inode limiti, bar\u0131nd\u0131rd\u0131\u011f\u0131n\u0131z sitelerin profilinden \u00e7ok etkilenir. Basit vitrin ve blog siteleri i\u00e7in 40\u201360 bin inode genellikle yeterliyken, eklenti zengini WordPress kurulumlar\u0131 ve WooCommerce ma\u011fazalar\u0131nda 100\u2013200 bin inode seviyeleri daha ger\u00e7ek\u00e7idir. Reseller seviyesinde pratik yakla\u015f\u0131m; Starter paketlerde 40\u201360 bin, Businessu201ta 80\u2013120 bin, Pro\/E\u2011ticarette ise 150\u2013250 bin aral\u0131\u011f\u0131nda limitler tan\u0131mlamakt\u0131r. Ayr\u0131ca m\u00fc\u015fterilere d\u00fczenli temizlik, eski yedekleri kald\u0131rma ve cache klas\u00f6rlerini kontrol etme al\u0131\u015fkanl\u0131\u011f\u0131n\u0131 kazand\u0131rman\u0131z, inode bask\u0131s\u0131n\u0131 ciddi bi\u00e7imde azaltacakt\u0131r.&#8221;<br \/>\n    },<br \/>\n    {<br \/>\n      &#8220;question&#8221;: &#8220;Ajans\u0131m i\u00e7in reseller mi, yoksa do\u011frudan VPS mi tercih etmeliyim?&#8221;,<br \/>\n      &#8220;answer&#8221;: &#8220;5\u201330 site aral\u0131\u011f\u0131ndaki ajanslar i\u00e7in iyi tasarlanm\u0131\u015f bir cPanel reseller paketi \u00e7o\u011fu zaman en verimli ba\u015flang\u0131\u00e7 noktas\u0131d\u0131r. \u00c7\u00fcnk\u00fc altyap\u0131 y\u00f6netimi, g\u00fcvenlik g\u00fcncellemeleri ve donan\u0131m taraf\u0131 DCHost ekibi taraf\u0131ndan y\u00f6netilir; siz projelere odaklan\u0131rs\u0131n\u0131z. Ancak 30\u201340 siteyi ge\u00e7meye, WooCommerce ve benzeri a\u011f\u0131r projelerin say\u0131s\u0131 artmaya ve kaynak limitleri s\u00fcrekli zorlanmaya ba\u015flad\u0131ysa, y\u00f6netilen VPS veya dedicated \u00e7\u00f6z\u00fcmler daha mant\u0131kl\u0131 hale gelir. K\u0131saca: Az say\u0131da hafif site \u2192 reseller; \u00e7ok say\u0131da veya a\u011f\u0131r site \u2192 kademeli olarak VPS\/dedicated mimarisine ge\u00e7i\u015f stratejisi en sa\u011fl\u0131kl\u0131 yoldur.&#8221;<br \/>\n    },<br \/>\n    {<br \/>\n      &#8220;question&#8221;: &#8220;Reseller paketinde e\u2011posta g\u00f6nderim limitini nas\u0131l belirlemeliyim?&#8221;,<br \/>\n      &#8220;answer&#8221;: &#8220;E\u2011posta taraf\u0131nda ama\u00e7, hem m\u00fc\u015fterilerin i\u015fini g\u00f6rmesi hem de IP itibar\u0131n\u0131z\u0131 korumakt\u0131r. K\u00fc\u00e7\u00fck kurumsal siteler i\u00e7in 100\u2013200 mail\/saat, biraz daha aktif b\u00fclten kullanan m\u00fc\u015fteriler i\u00e7in 300\u2013500 mail\/saat genellikle yeterlidir. Daha y\u00fcksek hacimli pazarlama g\u00f6nderimlerinde 800\u20131000 mail\/saat limitine \u00e7\u0131k\u0131labilir, fakat bu m\u00fc\u015fterileri m\u00fcmk\u00fcnse ayr\u0131 IP veya ayr\u0131 altyap\u0131da tutmak daha g\u00fcvenlidir. Ayr\u0131ca SPF, DKIM, DMARC ve rDNS kay\u0131tlar\u0131n\u0131 do\u011fru kurmak ve \u015f\u00fcpheli g\u00f6nderimleri loglardan takip etmek, limitlerin tek ba\u015f\u0131na \u00e7\u00f6zemeyece\u011fi spam risklerini ciddi oranda d\u00fc\u015f\u00fcr\u00fcr.&#8221;<br \/>\n    },<br \/>\n    {<br \/>\n      &#8220;question&#8221;: &#8220;CPU ve Entry Processes limitleri d\u00fc\u015f\u00fckt\u00fcr diye m\u00fc\u015fteri performans kayb\u0131 ya\u015far m\u0131?&#8221;,<br \/>\n      &#8220;answer&#8221;: &#8220;Tek ba\u015f\u0131na u201cd\u00fc\u015f\u00fck g\u00f6r\u00fcnenu201d CPU veya Entry Processes (EP) rakamlar\u0131, her zaman performans kayb\u0131 anlam\u0131na gelmez. \u0130yi cache alan, CDN kullanan, veritaban\u0131 sorgular\u0131 optimize edilmi\u015f bir WordPress sitesi, 0.25\u20130.5 vCPU ve 15\u201325 EP ile olduk\u00e7a ak\u0131c\u0131 \u00e7al\u0131\u015fabilir. Performans problemleri \u00e7o\u011fu zaman yetersiz \u00f6nbellekleme, a\u011f\u0131r eklentiler ve optimize edilmemi\u015f sorgulardan kaynaklan\u0131r. Bu y\u00fczden m\u00fc\u015fteri \u015fik\u00e2yetlerinde sadece limiti y\u00fckseltmek yerine, \u00f6nce uygulama d\u00fczeyinde optimizasyon yapmak; ard\u0131ndan gerekliyse paketi Business\/Pro seviyesine ta\u015f\u0131mak \u00e7ok daha sa\u011fl\u0131kl\u0131 ve s\u00fcrd\u00fcr\u00fclebilir bir yakla\u015f\u0131m olacakt\u0131r.&#8221;<br \/>\n    }<br \/>\n  ]<br \/>\n}<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>{ &#8220;title&#8221;: &#8220;cPanel Reseller Paket Tasar\u0131m\u0131: CPU, inode, Disk ve E\u2011Posta Limitlerini Do\u011fru Kurgulamak&#8221;, &#8220;content&#8221;: &#8220;n cPanel reseller kullan\u0131rken teknik olarak elinizde k\u0131s\u0131tl\u0131 ama payla\u015f\u0131labilir bir kaynak havuzu var: CPU, RAM, disk, inode, IO, e\u2011posta kapasitesi\u2026 Bu havuzu do\u011fru b\u00f6l\u00fc\u015ft\u00fcrmedi\u011finizde iki u\u00e7 sorunla kar\u015f\u0131la\u015f\u0131rs\u0131n\u0131z: Ya agresif limitler y\u00fcz\u00fcnden m\u00fc\u015fteriler s\u00fcrekli k\u0131s\u0131tlamaya tak\u0131l\u0131r, ya da a\u015f\u0131r\u0131 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4068,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4067","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\/4067","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=4067"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4067\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4068"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4067"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4067"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4067"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}