Re: Begin Daylight Savings Time Problems
- From: "John Spaith [MS]" <jspaith@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 12 Apr 2006 17:58:56 -0700
I just realized from my previous post there may be some more clever &
eloquent way to determine thread activity times, like one of the remote
tools. I'm pretty command line driven still so I'm can't offer much advice
on that.
--
John Spaith
Development Lead, Windows CE
Microsoft Corporation
Check out the CE Networking Team Blog at http://blogs.msdn.com/cenet/.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2006 Microsoft Corporation. All rights
reserved.
"John Spaith [MS]" <jspaith@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eRUtAVpXGHA.3840@xxxxxxxxxxxxxxxxxxxxxxx
Do you have the time service (timesvc.dll) on this device by any chance?
If you have the auto-DST functionality included in it, it will detect when
the DST cross-over is made regardless of whether or not you have it
actively enabled in the registry via the "AutoDST" setting. It does this
for book-keeping so that it knows whether it's in DST or STD time. If you
don't have timesvc, it's possible that some other app is doing this
book-keeping for itself.
That said, like you I'm surprised that your CPU is spiking like this for
so long. Is there any chance you could get a full debug build of the OS
and start turning on DEBUGZONE's until we see what's doing all the work?
Or if you capture what thread is taking all the CPU usage -- to do this,
in the target control window do a 'gi thrd' and then see CPU usages and
then break into the debugger and list the threads out in question and send
us the call stack.
--
John Spaith
Development Lead, Windows CE
Microsoft Corporation
Check out the CE Networking Team Blog at http://blogs.msdn.com/cenet/.
This posting is provided "AS IS" with no warranties, and confers no
rights.
You assume all risk for your use. © 2006 Microsoft Corporation. All rights
reserved.
"Bill T" <BillT@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:65B9F358-6A24-443A-ADC9-B5AFEBDE3D95@xxxxxxxxxxxxxxxx
Last weekend when daylight savings time began at 2:00 am April 2, 2006 we
noticed high processor loading for ~20 seconds on our CE 5.0 X86
platforms.
This is a bit surprising because I have disabled automatic daylight
savings
time handling for both the RTC hardware (Daylight Savings Time enable bit
is
cleared) and for the taskmanager (defined NODSTSAMPLE environment
variable).
Since then, I created a test app that sets the RTC to 1:59:50 am April 2,
2006, waits 20 seconds and then continuously repeats the sequence. When
I
run this along with the perfomance monitor tool, processor loading for
device.exe is >95% for ~10 seconds then goes to 0 for the another 10
seconds.
If I set the RTC so that the beginning of daylight savings time does not
occur, then there are short duration small processor loading spikes that
coincide with calls to SetLocalTime() in the app. There are a few things
that I questions about from these observations.
1. Why is device.exe exhibiting processor loading when SetLocalTime() is
called from the app?
2. What causes the large procesor loading in dvice.exe when the daylight
savings begin time occurs?
Thanks
.
- Follow-Ups:
- Re: Begin Daylight Savings Time Problems
- From: Bill T
- Re: Begin Daylight Savings Time Problems
- From: Bill T
- Re: Begin Daylight Savings Time Problems
- From: Bill T
- Re: Begin Daylight Savings Time Problems
- References:
- Re: Begin Daylight Savings Time Problems
- From: John Spaith [MS]
- Re: Begin Daylight Savings Time Problems
- Prev by Date: Re: Begin Daylight Savings Time Problems
- Next by Date: Re: Installation of Networked Media Device Feature Pack
- Previous by thread: Re: Begin Daylight Savings Time Problems
- Next by thread: Re: Begin Daylight Savings Time Problems
- Index(es):
Relevant Pages
|