Groups > comp.lang.java.programmer > #21396

Re: Threads, waiting for last one to finish

From	Arved Sandstrom <asandstrom2@eastlink.ca>
Newsgroups	comp.lang.java.programmer
Subject	Re: Threads, waiting for last one to finish
References	(1 earlier) <9TcIs.35775$tK1.985@newsfe07.iad> <afp4f896lcn7ltgi5djo47l81e080di5bv@4ax.com> <bUzIs.50596$On7.39770@newsfe16.iad> <d7u6f814793f29ko2bb93ajb62v6969i09@4ax.com> <50f37adc$0$293$14726298@news.sunsite.dk>
Message-ID	<XyQIs.80225$pV4.30405@newsfe21.iad> (permalink)
Organization	Public Usenet Newsgroup Access
Date	2013-01-14 05:51 -0400

Show all headers | View raw

On 01/13/2013 11:26 PM, Arne Vajhøj wrote:
> On 1/13/2013 10:18 PM, Roedy Green wrote:
>> On Sun, 13 Jan 2013 10:53:58 -0400, Arved Sandstrom
>> <asandstrom2@eastlink.ca> wrote, quoted or indirectly quoted someone
>> who said :
>>> As for threads taking different times, and "hanging around", I don't see
>>> the problem. If each individual thread does resource cleanup - like
>>> connections - before calling await(), what is the issue with a thread
>>> doing basically nothing?
>>
>> does not a thread have 1 MB + overhead just for existing?
>
> Yes, no, it depends.
>
> It is implementation dependent so it can and do differ between
> different vendors and platforms.
>
> Some may provide an option for changing the default.
>
> I have once read that SUN/Oracle Java on Windows and Linux uses
> 320 KB and 1024KB as default on 32 and 64 bit respectively.
>
> SUN/Oracle Java do provide the -Xss option to change the
> default.
>
> Arne
>
I use the -Xss on occasion for some apps, sometimes it's part of their 
tuning docs. Usually I don't worry about thread stack size, not if I've 
got a relatively small number (25 certainly being small) of threads.

Not when I need GB of memory for heap, and hundreds of megs for perm gen.

My approach here is my usual approach - go for a simple design, and if a 
quick gut-check of performance implications raises no red flags then go 
with that for implementation.

AHS

Thread

Threads, waiting for last one to finish Roedy Green <see_website@mindprod.com.invalid> - 2013-01-11 13:56 -0800
  Re: Threads, waiting for last one to finish markspace <markspace@nospam.nospam> - 2013-01-11 14:05 -0800
    Re: Threads, waiting for last one to finish Roedy Green <see_website@mindprod.com.invalid> - 2013-01-11 14:14 -0800
      Re: Threads, waiting for last one to finish markspace <markspace@nospam.nospam> - 2013-01-11 15:11 -0800
        Re: Threads, waiting for last one to finish Arne Vajhøj <arne@vajhoej.dk> - 2013-01-11 20:02 -0500
        Re: Threads, waiting for last one to finish Roedy Green <see_website@mindprod.com.invalid> - 2013-01-12 01:51 -0800
        Re: Threads, waiting for last one to finish Roedy Green <see_website@mindprod.com.invalid> - 2013-01-12 02:20 -0800
          Re: Threads, waiting for last one to finish Arne Vajhøj <arne@vajhoej.dk> - 2013-01-12 09:08 -0500
        Re: Threads, waiting for last one to finish Roedy Green <see_website@mindprod.com.invalid> - 2013-01-12 10:36 -0800
          Re: Threads, waiting for last one to finish Arne Vajhøj <arne@vajhoej.dk> - 2013-01-12 16:17 -0500
    Re: Threads, waiting for last one to finish Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2013-01-12 23:39 -0800
      Re: Threads, waiting for last one to finish Arne Vajhøj <arne@vajhoej.dk> - 2013-01-13 22:35 -0500
        Re: Threads, waiting for last one to finish Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2013-01-14 09:12 -0800
        Re: Threads, waiting for last one to finish Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2013-01-14 22:29 -0800
          Re: Threads, waiting for last one to finish markspace <markspace@nospam.nospam> - 2013-01-15 08:19 -0800
            Re: Threads, waiting for last one to finish Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2013-01-16 01:28 -0800
              Re: Threads, waiting for last one to finish Robert Klemme <shortcutter@googlemail.com> - 2013-01-20 15:21 +0100
            Re: Threads, waiting for last one to finish Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2013-01-18 21:58 -0800
      Re: Threads, waiting for last one to finish Robert Klemme <shortcutter@googlemail.com> - 2013-01-26 17:20 +0100
  Re: Threads, waiting for last one to finish Knute Johnson <nospam@knutejohnson.com> - 2013-01-11 21:19 -0800
    Re: Threads, waiting for last one to finish Robert Klemme <shortcutter@googlemail.com> - 2013-01-13 19:38 +0100
      Re: Threads, waiting for last one to finish Knute Johnson <nospam@knutejohnson.com> - 2013-01-14 08:58 -0800
      Re: Threads, waiting for last one to finish Arved Sandstrom <asandstrom2@eastlink.ca> - 2013-01-15 05:05 -0400
  Re: Threads, waiting for last one to finish Arved Sandstrom <asandstrom2@eastlink.ca> - 2013-01-12 08:42 -0400
    Re: Threads, waiting for last one to finish Roedy Green <see_website@mindprod.com.invalid> - 2013-01-12 23:56 -0800
      Re: Threads, waiting for last one to finish Arved Sandstrom <asandstrom2@eastlink.ca> - 2013-01-13 10:53 -0400
        Re: Threads, waiting for last one to finish Roedy Green <see_website@mindprod.com.invalid> - 2013-01-13 19:18 -0800
          Re: Threads, waiting for last one to finish Arne Vajhøj <arne@vajhoej.dk> - 2013-01-13 22:26 -0500
            Re: Threads, waiting for last one to finish Arved Sandstrom <asandstrom2@eastlink.ca> - 2013-01-14 05:51 -0400
              Re: Threads, waiting for last one to finish Arne Vajhøj <arne@vajhoej.dk> - 2013-01-14 19:02 -0500
        Re: Threads, waiting for last one to finish Roedy Green <see_website@mindprod.com.invalid> - 2013-01-13 19:43 -0800
  Re: Threads, waiting for last one to finish Sebastian <news@seyweiler.dyndns.org> - 2013-01-13 15:19 +0100

csiph-web