{"id":2571,"date":"2011-01-16T12:19:19","date_gmt":"2011-01-16T06:49:19","guid":{"rendered":"https:\/\/2thenew.online\/blog\/?p=2571"},"modified":"2016-11-30T12:47:49","modified_gmt":"2016-11-30T07:17:49","slug":"how-to-use-thread-pooling-using-groovy","status":"publish","type":"post","link":"https:\/\/2thenew.online\/blog\/how-to-use-thread-pooling-using-groovy\/","title":{"rendered":"How to use Thread-Pooling using Groovy"},"content":{"rendered":"

Grails Development is challenging and most Groovy and Grails <\/a>projects require in-depth understanding of thread-pooling.<\/p>\n

As a Groovy developer<\/a>, I really like the thread-pooling API (in java.util.concurrent package), especially when you are hitting x number of API dealing with outside network to fetch information for a single request.<\/p>\n

Example: A website dealing with some kind of ticket booking service and there are 4 different vendors (sources where you retrieve ticket status from).
\nClasses you need to import.<\/p>\n

[groovy]
\nimport java.util.concurrent.ExecutorService
\nimport java.util.concurrent.Executors
\nimport java.util.concurrent.Callable
\nimport java.util.concurrent.Executors
\nimport java.util.concurrent.TimeUnit
\nimport java.util.concurrent.Future
\n[\/groovy]<\/p>\n

I am discussing it here in a very simple Groovish manner.<\/p>\n

[groovy]
\ndef myClosure = {num -> println "I Love Groovy ${num}"}
\ndef threadPool = Executors.newFixedThreadPool(4)
\n try {
\n List<Future> futures = (1..10).collect{num->
\n threadPool.submit({->
\n myClosure num } as Callable);
\n }
\n \/\/ recommended to use following statement to ensure the execution of all tasks.
\n futures.each{it.get()}
\n}finally {
\n threadPool.shutdown()
\n}
\n[\/groovy]<\/p>\n

In the above example, thread pool size is 4, that means concurrent 4 tasks would be executed in a single go. And task is the code in ‘myClosure’.<\/p>\n

Let’s say you rely on output from tasks. In such a case, \u00a0you need to do the following:<\/p>\n

[groovy]
\n Collection results = futures.collect{it.get()}
\n[\/groovy]<\/p>\n","protected":false},"excerpt":{"rendered":"

Grails Development is challenging and most Groovy and Grails projects require in-depth understanding of thread-pooling. As a Groovy developer, I really like the thread-pooling API (in java.util.concurrent package), especially when you are hitting x number of API dealing with outside network to fetch information for a single request. Example: A website dealing with some kind […]<\/p>\n","protected":false},"author":17,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":110,"footnotes":""},"categories":[7],"tags":[4840,4005,9,3954],"class_list":["post-2571","post","type-post","status-publish","format-standard","hentry","category-grails","tag-grails","tag-grails-development","tag-groovy","tag-groovy-developer"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t