My account: Login | Sign Up
Loading... 

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:

1) Top Contributing Authors
2) Related Threads on "eBay Auctions"
3) Related Threads on Other Sites

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
Site: Discussions in microsoft.public.dotnet.framework  Discussions in microsoft.public.dotnet.framework - site profile
Forum: microsoft.public.dotnet.framework  microsoft.public.dotnet.framework - forum profile
Total authors: 3 authors
Total thread posts: 10 posts
Thread activity: no new posts during last week
Domain info for: microsoft.com

Thread posts in Performance hit because of Datetime.Now in microsoft.public.dotnet.framework:

1. 
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: - - - - - - - - - - -...
Size: 1,042 bytes
Customize:  Customize "Performance hit because of Datetime.Now in microsoft.public.dotnet.framework :: microsoft.public.dotnet.framework :: Discussions in microsoft.public.dotnet.framework"
2. 
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 ...
Size: 1,499 bytes
Customize:  Customize "<b>Reply 1</b>: Performance hit because of Datetime.Now in microsoft.public.dotnet.framework :: microsoft.public.dotnet.framework :: Discussions in microsoft.public.dotnet.framework"
3. 
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 > > ...
Size: 2,156 bytes
Customize:  Customize "<b>Reply 2</b>: Performance hit because of Datetime.Now in microsoft.public.dotnet.framework :: microsoft.public.dotnet.framework :: Discussions in microsoft.public.dotnet.framework"
4. 
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 ...
Size: 1,067 bytes
Customize:  Customize "<b>Reply 3</b>: Performance hit because of Datetime.Now in microsoft.public.dotnet.framework :: microsoft.public.dotnet.framework :: Discussions in microsoft.public.dotnet.framework"
5. 
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,  ...
Size: 2,182 bytes
Customize:  Customize "<b>Reply 4</b>: Performance hit because of Datetime.Now in microsoft.public.dotnet.framework :: microsoft.public.dotnet.framework :: Discussions in microsoft.public.dotnet.framework"
6. 
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 ...
Size: 3,869 bytes
Customize:  Customize "<b>Reply 5</b>: Performance hit because of Datetime.Now in microsoft.public.dotnet.framework :: microsoft.public.dotnet.framework :: Discussions in microsoft.public.dotnet.framework"
7. 
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. > > > ...
Size: 2,790 bytes
Customize:  Customize "<b>Reply 6</b>: Performance hit because of Datetime.Now in microsoft.public.dotnet.framework :: microsoft.public.dotnet.framework :: Discussions in microsoft.public.dotnet.framework"
8. 
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 ...
Size: 1,798 bytes
Customize:  Customize "<b>Reply 7</b>: Performance hit because of Datetime.Now in microsoft.public.dotnet.framework :: microsoft.public.dotnet.framework :: Discussions in microsoft.public.dotnet.framework"
9. 
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 > > ...
Size: 3,197 bytes
Customize:  Customize "<b>Reply 8</b>: Performance hit because of Datetime.Now in microsoft.public.dotnet.framework :: microsoft.public.dotnet.framework :: Discussions in microsoft.public.dotnet.framework"
10. 
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:  Customize "<b>Reply 9</b>: Performance hit because of Datetime.Now in microsoft.public.dotnet.framework :: microsoft.public.dotnet.framework :: Discussions in microsoft.public.dotnet.framework"
 

Top contributing authors for Performance hit because of Datetime.Now in microsoft.public.dotnet.framework

Name
Posts
chivateatul@gmail.com
4
user's latest post:
Performance hit because of...
Published (2008-10-01 13:09:00)
&nbsp; On Oct 1, 3:48pm, Brian Gideon &lt;briangid...@yahoo.com&gt; wrote: &gt; On Oct 1, 1:23pm, chivatea...@gmail.com wrote: &gt; &gt; &gt; Actually I am writing a gui in winform, which handles live data, &amp; &gt; &gt; that data is displayed in a grid(3rd party grid), in which when any &gt; &gt; cell has to paint it raises event for each cell &amp; in that event &gt; &gt;...
Brian Gideon
3
user's latest post:
Performance hit because of...
Published (2008-10-01 12:53:00)
&nbsp; On Oct 1, 1:23pm, chivatea...@gmail.com wrote: &gt; Actually I am writing a gui in winform, which handles live data, &amp; &gt; that data is displayed in a grid(3rd party grid), in which when any &gt; cell has to paint it raises event for each cell &amp; in that event &gt; depending on our business logic, we need to take datetime.now &amp; the &gt; previous datetime.Now, to know the timedifference...
Peter Duniho
3
user's latest post:
Performance hit because of...
Published (2008-10-01 17:23:00)
&nbsp; On Wed, 01 Oct 2008 13:04:15 -0700, &lt;chivateatul@gmail.com&gt; wrote: &gt; [...] &gt; We know Datetime.Now is not a bottleneck in the gui, or as I mentioned &gt; our gui is handling all tghose updates very efficiently but for &gt; further improvement, there are many small things and each contribute &gt; little penny and now we have to clear all those little things :-), and &gt; in that context...