Reply to thread

Message

Yeah Shawn, you're very right!
The "make it stable" / "use profilers" / "optimize where it's really needed" approach happens to be the most efficient IMHO!

It's very easy to optimize parts that don't slow down the application AT ALL... and code-optimizing is a never-ending process...

If you can detect real bottlenecks at first sight.... congratulations!
But I am often *very* surprised where the time really flies away when reading profiler results, so I simply gave up guessing where bottlenecks could be... use profilers!!

Keep hackin'

Daniel

btw: At the job, I use AQTime http://www.automatedqa.com/products/aqnet.asp (for Delphi, but there's a .NET version). Not very cheap but simply awesome once you get used to it!!

<blockquote data-quote="waeberd" data-source="post: 6791" data-attributes="member: 10343">Yeah Shawn, you're very right! The &quot;make it stable&quot; / &quot;use profilers&quot; / &quot;optimize where it's really needed&quot; approach happens to be the most efficient IMHO!It's very easy to optimize parts that don't slow down the application AT ALL... and code-optimizing is a never-ending process...If you can detect real bottlenecks at first sight.... congratulations! But I am often *very* surprised where the time really flies away when reading profiler results, so I simply gave up guessing where bottlenecks could be... use profilers!!Keep hackin' <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Danielbtw: At the job, I use AQTime <a href="http://www.automatedqa.com/products/aqnet.asp" target="_blank">http://www.automatedqa.com/products/aqnet.asp</a> (for Delphi, but there's a .NET version). Not very cheap but simply awesome once you get used to it!!</blockquote>

[QUOTE="waeberd, post: 6791, member: 10343"] Yeah Shawn, you're very right! The "make it stable" / "use profilers" / "optimize where it's really needed" approach happens to be the most efficient IMHO! It's very easy to optimize parts that don't slow down the application AT ALL... and code-optimizing is a never-ending process... If you can detect real bottlenecks at first sight.... congratulations! But I am often *very* surprised where the time really flies away when reading profiler results, so I simply gave up guessing where bottlenecks could be... use profilers!! Keep hackin' :) Daniel btw: At the job, I use AQTime [url]http://www.automatedqa.com/products/aqnet.asp[/url] (for Delphi, but there's a .NET version). Not very cheap but simply awesome once you get used to it!! [/QUOTE]