Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 08/27/2012 in all areas

  1. 1 point
    You could also use something like this and then parse out the X and Y values from it. LeftValues ( ExecuteSQL ( " SELECT Count (c_date) as thedate, Region FROM eqs7day_M1 WHERE c_date >= ? AND c_date <= ? GROUP BY Region ORDER BY thedate DESC " ; "" ; ""; global::dateStart; global::dateEnd ) ; 5 ) or LeftValues ( ExecuteSQL ( " SELECT Count (c_date) as thedate, Region FROM eqs7day_M1 WHERE c_date BETWEEN ? AND ? GROUP BY Region ORDER BY thedate DESC " ; "" ; ""; global::dateStart; global::dateEnd ) ; 5 )
  2. 1 point
    I agree with Markus - I have the same experience. In the past my company invested a lot of money to improve our server hardware, but we never saw the solution's performance improved by more than 20-30 % by that. We aso tried to go the long-term optimization path Markus is suggesting, but it was a lot of work and lot of guessing. Last year I discovered that the most efficient way to improve performance of our solution was to identify the real bottleneck (learn more about it at http://FMBench.com/bottleneck) and optimize just the bottleneck. However, sometimes it's hard to find the bottleneck even with FM Bench. For example FM Bench lets you easily identify a single script step as your bottleneck, but when the scrip step is a Set Field or something as atomic as that, you may need to go a bit deeper. My usual approach is then to make a copy of the solution, and keep deleting parts of it and examining how the performance is affected. You can, for example, delete half of all your tables. and then measure how long that "bottleneck" script step takes to execute. Is it significantly faster or not? If it is, then your real bottleneck is somewhere in the tables you have just deleted. If it's still very slow, then the bottleneck is in the half you have not deleted. And so on... You can replace your hardware, but at certain point you get to a level when better hardware won't help you because your solution won't be able to take advantage of the better hardware. But the solution itself - the algorithms, calculations, database structure - can be optimized and optimizing it will help you regardless of what hardware you use. So my suggestion is to never give up identifying the right bottleneck. Even if it's difficult, it is still the most efficient way to optimize your solution. I hope this helps... HOnza
This leaderboard is set to Los Angeles/GMT-08:00
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.