Richard Johnson wrote:
> It would be good if the Java reference platform had
> a java.util.Scheduler that perhaps configured itself
> with a policy object (java.util.SchedulerPolicy interface)
> whose implementations could do such things as query the system for
> resources (processor count, memory cap, et al) and set
> up its thread pool(s) and thread "metering" accordingly.
> The "reference" implementations in the jdk would unlikely
> meet everyone's notions or needs, but might aid in solving
> smallish thread allocation/use issues (in much the same
> way as the tree node cache implementations tap out
> when current tree capacity is reached <g>).
Ah, well there's another thing that would be tremendously useful - with or
without a java.util.Scheduler: a way to gauge a JVM's "busyness" so an app
could make its own loading decisions. Given the many limited resources one
can use up - threads, CPU, real and virtual memory, file descriptors, disk
space, and so on - and the unique behaviors of every platform, it's a nasty
problem to try to solve.
Nathan
>
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
