Hi
I havn't looked at java.nio but I will sure take a deeper look at it,
thanks for the tip.
/daniel
Avi Cherry wrote:
I don't have an exact answer to your question, but remember that each
thread has to contain a stack of its own, and therefore takes up
memory. The 'java.nio' (new i/o) package
Daniel Malmkvist wrote:
What I understand a thread pool will do lot pf unnessesary polling to
no good. But in the 1-thread per connection case the only resorces
that will be reserverd is a bit of memory (and on a 64 bit plattform
that is not a problem). Or am I missing anything, is there any
Éjmélyböl wrote:
2004-06-14, h keltezéssel 18:02-kor Daniel Malmkvist ezt írta:
Hi
I have a question about threads. I was wondering about what realy
happens to a thread on the OS level when i set it to read from a socket
when there is no data there. I use Native threads (not green threads).
Will
2004-06-14, h keltezéssel 18:02-kor Daniel Malmkvist ezt írta:
> Hi
>
> I have a question about threads. I was wondering about what realy
> happens to a thread on the OS level when i set it to read from a socket
> when there is no data there. I use Native threads (not green threads).
>
> Will the
Daniel Malmkvist wrote:
I have an application that should handle alot (>10 000) connection at
the same time but usally no traffic. Is the best way to make a thread
pool or is the best way to have 1 thread per connection. If no contex
switching will be done I don't see why not.
YOu will have a
I don't have an exact answer to your question, but remember that each
thread has to contain a stack of its own, and therefore takes up
memory. The 'java.nio' (new i/o) package in recent versions of Java
was designed for exactly this case that you're mentioning, where you
have a lot of connecti
Daniel Malmkvist said:
> Hi
>
> I have a question about threads. I was wondering about what realy
> happens to a thread on the OS level when i set it to read from a socket
> when there is no data there. I use Native threads (not green threads).
>
> Will the thread realy sleep, no contex switch will
Hi
I have a question about threads. I was wondering about what realy
happens to a thread on the OS level when i set it to read from a socket
when there is no data there. I use Native threads (not green threads).
Will the thread realy sleep, no contex switch will be done. The thread
will sleep u
Title: Thread question
I am using familiar linux with blackdown's jvm 1.3.1 on an ARM processor. I have no problem running separate processes, but I can't seem to get any threads to start. Is there something I need to set in the /proc file system to enable thread support?
Hi,
On Mon, 09 Nov 1998, Keith T. Garner wrote:
>I've been experimenting with the new native threading code, beating on it
>to see how it holds up, doing that sort of beta test that people dream of.
>(I've found a memory bug, but that's for a different piece of mail...)
>
>Anyway, while watching
I've been experimenting with the new native threading code, beating on it
to see how it holds up, doing that sort of beta test that people dream of.
(I've found a memory bug, but that's for a different piece of mail...)
Anyway, while watching the process table, I noticed that most of the
threads
11 matches
Mail list logo