Performance hit because of Datetime.Now in microsoft.public.dotnet.framework | Thread profile
Thread profile page for "Performance hit because of Datetime.Now in microsoft.public.dotnet.framework" on http://www.microsoft.com/communities/newsgroups....
This report page is a snippet summary view from a single thread "Performance hit because of Datetime.Now in microsoft.public.dotnet.framework", located on the Message Board at http://www.microsoft.com/communities/newsgroups....
This thread profile page shows the thread statistics for: Total Authors, Total Thread Posts, and Thread Activity, which are reported in a table below.
Additional thread profile information is also shown in the following ways:
Warning: These statistics are generated using 'best efforts' and can experience delays and reporting errors at times. Please note that such statistics do not constitute a thread's popularity and/or exact posting volumes at any given reporting period.
Title:
Performance hit because of Datetime.Now in microsoft.public.dotnet.framework
Started 2 months ago (2008-10-01 10:01:00)
by chivateatul@gmail.com
If DateTime.Now is called in a very large loop, it's a time consuming & also CPU utilization increases. Instead, getting current datetime by following way is much more efficient. So is there any performance issue with DateTime.Now? is this a correct way to get current datetime? Pseudo Code: - - - - - - - - - - -...
Started 2 months ago (2008-10-01 10:17:00)
by Brian Gideon
On Oct 1, 11:55 am, chivatea...@gmail.com wrote: > If DateTime.Now is called in a very large loop, it's a time consuming > & also CPU utilization increases. > Instead, getting current datetime by following way is much more > efficient. > > So is there any performance issue with DateTime.Now? is this a correct > way to get ...
Started 2 months ago (2008-10-01 10:37:00)
by chivateatul@gmail.com
On Oct 1, 1:10 pm, Brian Gideon <briangid...@yahoo.com> wrote: > On Oct 1, 11:55 am, chivatea...@gmail.com wrote: > > > > > > > If DateTime.Now is called in a very large loop, it's a time consuming > > & also CPU utilization increases. > > Instead, getting current datetime by following way is much more > > ...
Started 2 months ago (2008-10-01 10:45:00)
by Peter Duniho
On Wed, 01 Oct 2008 09:55:06 -0700, <chivateatul@gmail.com> wrote: > If DateTime.Now is called in a very large loop, it's a time consuming > & also CPU utilization increases. If you are calling DateTime.Now so often that it's a performance issue, then you probably should fix the underlying design so that you don't call ...
Started 2 months ago (2008-10-01 11:25:00)
by chivateatul@gmail.com
On Oct 1, 1:39 pm, "Peter Duniho" <NpOeStPe...@nnowslpianmk.com> wrote: > On Wed, 01 Oct 2008 09:55:06 -0700, <chivatea...@gmail.com> wrote: > > If DateTime.Now is called in a very large loop, it's a time consuming > > & also CPU utilization increases. > > If you are calling DateTime.Now so often that it's a performance issue, ...
Started 2 months ago (2008-10-01 12:11:00)
by Peter Duniho
On Wed, 01 Oct 2008 11:23:50 -0700, <chivateatul@gmail.com> wrote: > Actually I am writing a gui in winform, which handles live data, & > that data is displayed in a grid(3rd party grid), in which when any > cell has to paint it raises event for each cell & in that event > depending on our business logic, we need to take datetime.now ...
Started 2 months ago (2008-10-01 12:41:00)
by Brian Gideon
On Oct 1, 12:33 pm, chivatea...@gmail.com wrote: > On Oct 1, 1:10 pm, Brian Gideon <briangid...@yahoo.com> wrote: > > > > > > > On Oct 1, 11:55 am, chivatea...@gmail.com wrote: > > > > If DateTime.Now is called in a very large loop, it's a time consuming > > > & also CPU utilization increases. > > > ...
Started 2 months ago (2008-10-01 12:53:00)
by Brian Gideon
On Oct 1, 1:23 pm, chivatea...@gmail.com wrote: > Actually I am writing a gui in winform, which handles live data, & > that data is displayed in a grid(3rd party grid), in which when any > cell has to paint it raises event for each cell & in that event > depending on our business logic, we need to take datetime.now & the > previous ...
Started 2 months ago (2008-10-01 13:09:00)
by chivateatul@gmail.com
On Oct 1, 3:48 pm, Brian Gideon <briangid...@yahoo.com> wrote: > On Oct 1, 1:23 pm, chivatea...@gmail.com wrote: > > > Actually I am writing a gui in winform, which handles live data, & > > that data is displayed in a grid(3rd party grid), in which when any > > cell has to paint it raises event for each cell & in that event > > ...
Started 2 months ago (2008-10-01 17:23:00)
by Peter Duniho
On Wed, 01 Oct 2008 13:04:15 -0700, <chivateatul@gmail.com> wrote: > [...] > We know Datetime.Now is not a bottleneck in the gui, or as I mentioned > our gui is handling all tghose updates very efficiently but for > further improvement, there are many small things and each contribute > little penny and now we have to clear all ...
Size: 1,319 bytes
Customize:
Top contributing authors for Performance hit because of Datetime.Now in microsoft.public.dotnet.framework
On Oct 1, 3:48pm, Brian Gideon <briangid...@yahoo.com> wrote: > On Oct 1, 1:23pm, chivatea...@gmail.com wrote: > > > Actually I am writing a gui in winform, which handles live data, & > > that data is displayed in a grid(3rd party grid), in which when any > > cell has to paint it raises event for each cell & in that event > >...
On Oct 1, 1:23pm, chivatea...@gmail.com wrote: > Actually I am writing a gui in winform, which handles live data, & > that data is displayed in a grid(3rd party grid), in which when any > cell has to paint it raises event for each cell & in that event > depending on our business logic, we need to take datetime.now & the > previous datetime.Now, to know the timedifference...
On Wed, 01 Oct 2008 13:04:15 -0700, <chivateatul@gmail.com> wrote: > [...] > We know Datetime.Now is not a bottleneck in the gui, or as I mentioned > our gui is handling all tghose updates very efficiently but for > further improvement, there are many small things and each contribute > little penny and now we have to clear all those little things :-), and > in that context...
Related threads on "Discussions in microsoft.public.dotnet.framework":