On Sat, Jan 10, 2009 at 6:39 AM, downs wrote:
> Jarrett Billingsley wrote:
>> On Sat, Jan 10, 2009 at 12:30 AM, Jarrett Billingsley
>> wrote:
>>> On Sat, Jan 10, 2009 at 12:18 AM, yes wrote:
Does Phobos also do threadpools?
>>> From what I understand, not without modification. At least, no
Jarrett Billingsley wrote:
> On Sat, Jan 10, 2009 at 12:30 AM, Jarrett Billingsley
> wrote:
>> On Sat, Jan 10, 2009 at 12:18 AM, yes wrote:
>>> Does Phobos also do threadpools?
>> From what I understand, not without modification. At least, not
>> efficiently. Downs has implemented such a thing
On Sat, Jan 10, 2009 at 12:18 AM, yes wrote:
> Does Phobos also do threadpools?
>From what I understand, not without modification. At least, not
efficiently. Downs has implemented such a thing in scrapple.tools,
but it requires a patch to Phobos to make it run at a reasonable
speed.
> Somehow
On Sat, Jan 10, 2009 at 12:30 AM, Jarrett Billingsley
wrote:
> On Sat, Jan 10, 2009 at 12:18 AM, yes wrote:
>> Does Phobos also do threadpools?
>
> From what I understand, not without modification. At least, not
> efficiently. Downs has implemented such a thing in scrapple.tools,
> but it requi
Does Phobos also do threadpools?
Somehow I liked the idea of an Object like agent smith, just duplicate yourself
when the task is too big. ( ^_^ )
>
>
> Hm... I guess I understand now, you need a task parallelization, right?
>
> In order to do this, you usually separate the task into several
On Sat, 10 Jan 2009 07:32:43 +0300, yes wrote:
What does this code do? It looks like a ThreadPool use case but I might
be wrong.
I tried to recursively make an object distribute its calculations.
The calculations should take at least a minute.
Hm... I guess I understand now, you need
>
> What does this code do? It looks like a ThreadPool use case but I might be
> wrong.
>
I tried to recursively make an object distribute its calculations.
The calculations should take at least a minute.
On Sat, 10 Jan 2009 05:44:20 +0300, yes wrote:
How bad is the following idea?
class Calc
{
void addThread()
{
Data data;
data = new Data();
}
void run()
{
if ( hardware threads > current threadcount)
{
addThread();
}
//wait for some signal
//run calculations on data / threads
}
}
Cal
How bad is the following idea?
class Calc
{
void addThread()
{
Data data;
data = new Data();
}
void run()
{
if ( hardware threads > current threadcount)
{
addThread();
}
//wait for some signal
//run calculations on data / threads
}
}
Calc mainCalc;
mainCalc = new Calc();
mainCalc.run();
