ndup:
>>>>>> http://www.tutelman.com/golf/measure/precision.php )
>>>>>
>>>>>
>>>>>
>>>>> I'm not sure about the others, but as an Electrical Engineer, I know the
>>>>> difference between resolution, prec
t;>>>
>>>>
>>>>
>>>> I'm not sure about the others, but as an Electrical Engineer, I know the
>>>> difference between resolution, precision, and accuracy. In the post I
>>>> made
>>>> earlier, I said and meant "resol
ally called "accuracy".
>>>>> (also see "precision" , here is a good roundup:
>>>>> http://www.tutelman.com/golf/measure/precision.php )
>>>>
>>>>
>>>>
>>>> I'm not sure about the others,
>>> I'm not sure about the others, but as an Electrical Engineer, I know the
>>> difference between resolution, precision, and accuracy. In the post I
>>> made
>>> earlier, I said and meant "resolution".
>>>
>>>
>>>
>>
onstantin Preißer [mailto:kpreis...@apache.org]
Sent: 31. October 2015 10:27
To: Tomcat Users List
Subject: [OT] RE: 80ms delay switching between worker threads
Importance: Low
Hi Christopher,
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Sat
tware Engineer
www.comtrade.com
-Original Message-
From: Konstantin Preißer [mailto:kpreis...@apache.org]
Sent: 31. October 2015 10:27
To: Tomcat Users List
Subject: [OT] RE: 80ms delay switching between worker threads
Importance: Low
Hi Christopher,
-Original Message-
Fro
ade.com
>>
>>> -Original Message-----
>>> From: Konstantin Preißer [mailto:kpreis...@apache.org]
>>> Sent: 31. October 2015 10:27
>>> To: Tomcat Users List
>>> Subject: [OT] RE: 80ms delay switching between worker threads
>>> Importan
Farzad,
On 10/31/15 2:11 AM, Farzad Panahi wrote:
> Hi Chris - I am using a linux instance on amazon cloud.
You may be seeing either of the following:
1. Loss of real-time clock resolution due to virtualization
(or support from the host OS)
2. Delays imposed on your instance by the hypervisor
ailto:kpreis...@apache.org]
Sent: 31. October 2015 10:27
To: Tomcat Users List
Subject: [OT] RE: 80ms delay switching between worker threads
Importance: Low
Hi Christopher,
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Saturday, October 31, 2
-Original Message-
> From: Konstantin Preißer [mailto:kpreis...@apache.org]
> Sent: 31. October 2015 10:27
> To: Tomcat Users List
> Subject: [OT] RE: 80ms delay switching between worker threads
> Importance: Low
>
> Hi Christopher,
>
> > -Original Message-
>
Hi Christopher,
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Saturday, October 31, 2015 3:43 AM
>
> What OS are you using? IIRC, the Windows timer has horrible resolution.
> you can call System.currentTimeNanos all you want, but you won't
Hi Chris - I am using a linux instance on amazon cloud.
On Oct 30, 2015 7:43 PM, "Christopher Schultz"
wrote:
> Farzad,
>
> On 10/30/15 6:10 PM, Farzad Panahi wrote:
> > Thanks for the explanation David.
> >
> > I added System.nanoTime() to get high resolution numbers. Nano second
> > numbers are
Farzad,
On 10/30/15 6:10 PM, Farzad Panahi wrote:
> Thanks for the explanation David.
>
> I added System.nanoTime() to get high resolution numbers. Nano second
> numbers are telling me the same thing. When thread changes we see a
> difference of about 82ms (3082462134714 - 3082379268473 = 8286624
Thanks for the explanation David.
I added System.nanoTime() to get high resolution numbers. Nano second
numbers are telling me the same thing. When thread changes we see a
difference of about 82ms (3082462134714 - 3082379268473 = 82866241).
Within the same thread the time difference is something b
On 10/30/2015 3:23 PM, Farzad Panahi wrote:
Mark - Could you elaborate a bit more on what you mean by "resolution
of the timestamps for the log messages"? If you are referring to the
log4j latency (https://logging.apache.org/log4j/2.x/manual/async.html#Latency),
it is in microseconds.
If it has
Mark - Could you elaborate a bit more on what you mean by "resolution
of the timestamps for the log messages"? If you are referring to the
log4j latency (https://logging.apache.org/log4j/2.x/manual/async.html#Latency),
it is in microseconds.
If it has anything to do with the logger why is it happ
André - I like your humour :D
On Fri, Oct 30, 2015 at 1:38 AM, André Warnier (tomcat) wrote:
> On 30.10.2015 01:03, Farzad Panahi wrote:
>>
>> Hi,
>>
>> I am using tomcat 8.0.23 to terminate my websocket connections. I was
>> looking at my trace logs and noticed that when tomcat worker thread
>>
On 30/10/2015 00:03, Farzad Panahi wrote:
> Hi,
>
> I am using tomcat 8.0.23 to terminate my websocket connections. I was
> looking at my trace logs and noticed that when tomcat worker thread
> responsible for processing websocket messages switches to a different
> thread, there is about 80ms dela
On 30.10.2015 01:03, Farzad Panahi wrote:
Hi,
I am using tomcat 8.0.23 to terminate my websocket connections. I was
looking at my trace logs and noticed that when tomcat worker thread
responsible for processing websocket messages switches to a different
thread, there is about 80ms delay. In my O
Hi,
I am using tomcat 8.0.23 to terminate my websocket connections. I was
looking at my trace logs and noticed that when tomcat worker thread
responsible for processing websocket messages switches to a different
thread, there is about 80ms delay. In my OnMessage implementation I
let the work done
20 matches
Mail list logo
