From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,b3258fa06e2efdf3
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-05-01 18:14:42 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn13feed!wn12feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!rwcrnsc54.POSTED!not-for-mail
From: tmoran@acm.org
Newsgroups: comp.lang.ada
Subject: Re: Tasks unleashed
References: <MPG.191b473be18428019896f1@News.CIS.DFN.DE>
X-Newsreader: Tom's custom newsreader
Message-ID: <5Ejsa.430589$OV.427578@rwcrnsc54>
NNTP-Posting-Host: 12.234.13.56
X-Complaints-To: abuse@attbi.com
X-Trace: rwcrnsc54 1051838081 12.234.13.56 (Fri, 02 May 2003 01:14:41 GMT)
NNTP-Posting-Date: Fri, 02 May 2003 01:14:41 GMT
Organization: AT&T Broadband
Date: Fri, 02 May 2003 01:14:41 GMT
Xref: archiver1.google.com comp.lang.ada:36827
Date: 2003-05-02T01:14:41+00:00
List-Id: <comp.lang.ada>

>In any case, the memory thing forces to use pools of reusable tasks,
>it's my main and crucial conclusion.

  Have you considered a protected Buffer of work to do and a fixed pool of
tasks which queue on an entry waiting for the Buffer to have some work to
do (or instructions to quit)?  Then you needn't create or destroy the
worker tasks.