Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #28117
| Path | csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.CARNet.hr!gregory.BNet.hr!not-for-mail |
|---|---|
| From | Josip Almasi <joe@vrspace.org> |
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: thread pool with CachedThreadPool |
| Date | Thu, 17 Apr 2014 12:12:14 +0200 |
| Organization | B.net Hrvatska d.o.o. |
| Lines | 31 |
| Message-ID | <lio9du$ah$1@gregory.bnet.hr> (permalink) |
| References | <liirm6$1vl6$1@ariadne.rz.tu-clausthal.de> <12vmb157ulwwb.1cmusyz7wuuyi$.dlg@40tude.net> <lij2aj$217t$1@ariadne.rz.tu-clausthal.de> <H2i3v.81309$aK5.58575@fx24.iad> <br6n5eF4pmgU1@mid.individual.net> <lilmqh$feh$1@gregory.bnet.hr> <br7nfqFbmbrU1@mid.individual.net> <mcmurtrie-DCE798.22115916042014@c-61-68-245-199.per.connect.net.au> |
| NNTP-Posting-Host | cpe-94-253-152-146.zg.cable.xnet.hr |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=ISO-8859-1; format=flowed |
| Content-Transfer-Encoding | 7bit |
| X-Trace | gregory.bnet.hr 1397729534 337 94.253.152.146 (17 Apr 2014 10:12:14 GMT) |
| X-Complaints-To | abuse@globalnet.hr |
| NNTP-Posting-Date | Thu, 17 Apr 2014 10:12:14 +0000 (UTC) |
| User-Agent | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 |
| In-Reply-To | <mcmurtrie-DCE798.22115916042014@c-61-68-245-199.per.connect.net.au> |
| Xref | csiph.com comp.lang.java.programmer:28117 |
Show key headers only | View raw
On 04/17/2014 07:11 AM, Kevin McMurtrie wrote: > In article <br7nfqFbmbrU1@mid.individual.net>, > Robert Klemme <shortcutter@googlemail.com> wrote: > >> On 16.04.2014 12:42, Josip Almasi wrote: >>> >>> Blocked thread itself spends no cpu time. >>> Running thread may spend some more cpu time though, for lock checks. >>> Real issue is flushing pipeline to ensure cache coherency among all cpu >>> cores. >>> So, more 'synchronized' statements your single running thread >>> encounters, more cpu stalls. It's not really 'taking' cpu time, it's >>> wasting it. >> >> I don't think this applies. We were talking about threads idling in the >> pool. [snip] Probably so. But, see, it's not just 'small ammount of kernel time', issues go all the way to cpu design. > Sun's thread pools are garbage [snip] Dang. Thanks Kevin, you possibly saved me a lot of time. Regards...
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread
thread pool with CachedThreadPool Philipp Kraus <philipp.kraus@flashpixx.de> - 2014-04-15 10:47 +0200
Re: thread pool with CachedThreadPool Joerg Meier <joergmmeier@arcor.de> - 2014-04-15 12:02 +0200
Re: thread pool with CachedThreadPool Philipp Kraus <philipp.kraus@flashpixx.de> - 2014-04-15 12:40 +0200
Re: thread pool with CachedThreadPool Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2014-04-15 15:05 -0700
Re: thread pool with CachedThreadPool Robert Klemme <shortcutter@googlemail.com> - 2014-04-16 08:43 +0200
Re: thread pool with CachedThreadPool Josip Almasi <joe@vrspace.org> - 2014-04-16 12:42 +0200
Re: thread pool with CachedThreadPool Robert Klemme <shortcutter@googlemail.com> - 2014-04-16 17:55 +0200
Re: thread pool with CachedThreadPool Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2014-04-16 22:11 -0700
Re: thread pool with CachedThreadPool Josip Almasi <joe@vrspace.org> - 2014-04-17 12:12 +0200
csiph-web