{"id":7554,"date":"2024-12-24T16:00:17","date_gmt":"2024-12-24T13:00:17","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/java-executor-service-detayli-anlatim\/"},"modified":"2024-12-24T16:00:17","modified_gmt":"2024-12-24T13:00:17","slug":"java-executor-service-detayli-anlatim","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/java-executor-service-detayli-anlatim\/","title":{"rendered":"Java Executor Service: Detayl\u0131 Anlat\u0131m"},"content":{"rendered":"

<\/p>\n

Java Executor Service: Detayl\u0131 Anlat\u0131m<\/p>\n

Java’da paralel programlama, performans a\u00e7\u0131s\u0131ndan b\u00fcy\u00fck \u00f6nem ta\u015f\u0131r. Birden fazla g\u00f6revi e\u015f zamanl\u0131 olarak y\u00fcr\u00fctmek, uygulamalar\u0131n h\u0131zl\u0131 ve verimli \u00e7al\u0131\u015fmas\u0131n\u0131 sa\u011flar. Bu noktada, Executor Service devreye girer. Executor Service, thread y\u00f6netimini kolayla\u015ft\u0131ran ve performans\u0131 optimize eden g\u00fc\u00e7l\u00fc bir ara\u00e7t\u0131r. Basit\u00e7e anlatmak gerekirse, bir thread havuzudur ve g\u00f6revlerinizi bu havuzdaki i\u015f\u00e7ilere (threads) da\u011f\u0131t\u0131r. Bu sayede thread olu\u015fturma ve y\u00f6netimiyle u\u011fra\u015fmadan, i\u015finize odaklanabilirsiniz.<\/p>\n

Neden Executor Service Kullanmal\u0131y\u0131z?<\/h2>\n

Standart thread olu\u015fturma y\u00f6ntemleri, \u00e7ok say\u0131da g\u00f6revin y\u00f6netimini zorla\u015ft\u0131r\u0131r. Her g\u00f6rev i\u00e7in yeni bir thread olu\u015fturmak, kaynak t\u00fcketimine ve performans d\u00fc\u015f\u00fc\u015f\u00fcne yol a\u00e7abilir. Executor Service ise bu sorunu, \u00f6nceden tan\u0131mlanm\u0131\u015f bir thread havuzu kullanarak \u00e7\u00f6zer. Bu havuzdaki thread’ler tekrar kullan\u0131labilir, dolay\u0131s\u0131yla yeni thread olu\u015fturma maliyetinden kurtulmu\u015f oluruz. Ayr\u0131ca, Executor Service, thread’lerin y\u00f6netimini basitle\u015ftirerek, kodun daha okunakl\u0131 ve anla\u015f\u0131l\u0131r olmas\u0131n\u0131 sa\u011flar. Sonu\u00e7 olarak, Executor Service ile daha verimli ve \u00f6l\u00e7eklenebilir uygulamalar geli\u015ftirebiliriz.<\/p>\n

Executor Service’in Temel Bile\u015fenleri<\/h2>\n

Executor Service, temel olarak \u00fc\u00e7 ana bile\u015fenden olu\u015fur: ExecutorService<\/b> aray\u00fcz\u00fc, ThreadPoolExecutor<\/b> s\u0131n\u0131f\u0131 ve \u00e7e\u015fitli Factory<\/b> metotlar\u0131. ExecutorService aray\u00fcz\u00fc, thread’leri y\u00f6netmek i\u00e7in temel metotlar\u0131 tan\u0131mlar. ThreadPoolExecutor ise bu aray\u00fcz\u00fc uygulayan ve thread havuzunu y\u00f6neten bir s\u0131n\u0131ft\u0131r. Factory metotlar\u0131 ise \u00f6nceden yap\u0131land\u0131r\u0131lm\u0131\u015f thread havuzlar\u0131 olu\u015fturmay\u0131 kolayla\u015ft\u0131r\u0131r.<\/p>\n

ExecutorService Aray\u00fcz\u00fc<\/h3>\n

ExecutorService aray\u00fcz\u00fc, submit()<\/code>, execute()<\/code>, shutdown()<\/code> gibi \u00f6nemli metotlar\u0131 i\u00e7erir. submit()<\/code> metodu, bir g\u00f6revi (Runnable veya Callable) havuzuna g\u00f6nderir ve bir Future nesnesi d\u00f6nd\u00fcr\u00fcr. Bu nesne, g\u00f6revin sonucunu veya durumunu sorgulamak i\u00e7in kullan\u0131l\u0131r. execute()<\/code> metodu ise sadece g\u00f6revi havuzuna g\u00f6nderir. shutdown()<\/code> metodu ise havuzun yeni g\u00f6rev kabul etmesini durdurur. Havuzdaki mevcut g\u00f6revler tamamland\u0131ktan sonra havuz kapat\u0131l\u0131r.<\/p>\n

ThreadPoolExecutor S\u0131n\u0131f\u0131<\/h3>\n

ThreadPoolExecutor s\u0131n\u0131f\u0131, thread havuzunun detayl\u0131 konfig\u00fcrasyonunu sa\u011flar. Thread say\u0131s\u0131, kuyruk boyutu, redaksiyon politikas\u0131 gibi parametreler bu s\u0131n\u0131f arac\u0131l\u0131\u011f\u0131yla ayarlanabilir. \u00d6rne\u011fin, thread say\u0131s\u0131n\u0131 art\u0131rarak daha fazla g\u00f6revi e\u015f zamanl\u0131 olarak i\u015fleyebilir veya kuyruk boyutu art\u0131r\u0131larak g\u00f6revlerin birikmesini engelleyebilirsiniz. Yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f bir ThreadPoolExecutor performans sorunlar\u0131na yol a\u00e7abilir; bu y\u00fczden dikkatli bir konfig\u00fcrasyon \u00f6nemlidir.<\/p>\n

Factory Metotlar\u0131<\/h3>\n

Executors s\u0131n\u0131f\u0131, \u00f6nceden yap\u0131land\u0131r\u0131lm\u0131\u015f ExecutorService \u00f6rnekleri olu\u015fturmak i\u00e7in statik factory metotlar\u0131 sunar. Executors.newFixedThreadPool()<\/code>, belirli say\u0131da thread’den olu\u015fan sabit bir havuz olu\u015fturur. Executors.newCachedThreadPool()<\/code> ise gerekti\u011finde yeni thread’ler olu\u015fturan ve kullan\u0131lmayan thread’leri geri d\u00f6n\u00fc\u015ft\u00fcren bir havuz olu\u015fturur. Executors.newSingleThreadExecutor()<\/code>, tek bir thread ile \u00e7al\u0131\u015fan bir havuz olu\u015fturur. Do\u011fru factory metodunu se\u00e7mek, uygulama gereksinimlerine ba\u011fl\u0131d\u0131r.<\/p>\n

\u00d6rnek Kod<\/h2>\n

A\u015fa\u011f\u0131daki \u00f6rnek, Executors.newFixedThreadPool() kullanarak bir ExecutorService olu\u015fturur ve be\u015f g\u00f6revi havuzuna g\u00f6nderir:<\/p>\n

\nimport java.util.concurrent.ExecutorService;\nimport java.util.concurrent.Executors;\n\npublic class ExecutorServiceExample {\n    public static void main(String[] args) {\n        ExecutorService executor = Executors.newFixedThreadPool(5);\n\n        for (int i = 0; i < 5; i++) {\n            executor.execute(() -> {\n                System.out.println(\"G\u00f6rev \" + Thread.currentThread().getName() + \" \u00e7al\u0131\u015f\u0131yor.\");\n                \/\/ G\u00f6rev i\u015flemleri burada yap\u0131l\u0131r.\n            });\n        }\n\n        executor.shutdown();\n    }\n}\n<\/pre>\n
Sonu\u00e7<\/h2>\n
Java Executor Service, paralel programlamada performans ve verimlili\u011fi art\u0131rmak i\u00e7in g\u00fc\u00e7l\u00fc bir ara\u00e7t\u0131r.  Thread y\u00f6netimini basitle\u015ftirerek, uygulamalar\u0131n\u0131z\u0131n daha h\u0131zl\u0131 ve \u00f6l\u00e7eklenebilir olmas\u0131n\u0131 sa\u011flar.  Ancak, do\u011fru konfig\u00fcrasyon ve kullan\u0131m, performans optimizasyonu a\u00e7\u0131s\u0131ndan kritik \u00f6neme sahiptir.  Uygulama gereksinimlerinizi do\u011fru analiz ederek, en uygun Executor Service yap\u0131land\u0131rmas\u0131n\u0131 se\u00e7meniz \u00f6nemlidir.  Daha fazla bilgi i\u00e7in fatihsoysal.com<\/a> sitesini ziyaret edebilirsiniz.<\/p>\n
Ayr\u0131ca, Java Concurrency'e dair daha fazla bilgi i\u00e7in a\u015fa\u011f\u0131daki kaynaklara da g\u00f6z atabilirsiniz:<\/p>\n