>Got it and appreciate the reply.
No probs.
>I am using Win2K but it looks like the threading is behaving in a manner
similar NT.
That's what I thought. Before the marketing people kicked into action, Win2K/XP
was generally referred to as NT 5.0, so I'm not surprised that the thread
behaviour
i
> -Original Message-
> From: Martin Ramshaw [mailto:[EMAIL PROTECTED]]
>
>
> My experience with NT 4.0 was that it had a limit of 64
> threads (some of which were needed internally), which meant
> that the most I could use was approx. 58. NT 4.0 is [was?] a
> time-slice OS rather tha
My experience with NT 4.0 was that it had a limit of 64 threads (some of which
were needed internally), which meant that the most I could use was approx. 58.
NT 4.0 is [was?] a time-slice OS rather than a full multi-process OS which had
specific affects on thread processing. Perhaps MS fixed this
> I believe JMeter holds on to all the samples in memory, while
>the File listener lets go of them as soon as they are written
>to disk.
Isn't that only true if you have "Automatically Flush After Each Data Sample" checked
though?
Berin Loritsch <[EMAIL PROTECTED]> wrote: Are you running any
Not using any modification managers or graphical wizz-bang listeners. My guess is that
your 512Mb ram and the fact that you are running on linux makes the most difference. I
will try the hotspot VM and increasing the stack size though.
Thanks.
-David-
"Stover, Michael" <[EMAIL PROTECTE
Are you running any graphical listeners?
The best way to bump up performance is to use the File Listener,
and evaluate the results later. Otherwise the overhead of the
graphs are going to cause you problems.
I believe JMeter holds on to all the samples in memory, while
the File listener lets go
6 matches
Mail list logo
