by Overload » Thu Oct 30, 2008 10:20 pm
This restriction was originally put in a number of years ago when computers often ran at 750mhz with 512mb of RAM. At that time, such restrictions were necessary to make an automated search run at a reasonable pace, and without overloading a computer.
Computers run much faster now, so we could certainly eliminate this limitation, and we probably will at some point. But we've also learned over the years that an automated search will be much more efficient when it's focused on a specific time period and market rather than a search for everything all at once. For example, running a search for All Securities against a 25 year time frame would be an extremely slow search, and would probably not take advantage of the benefits that come from tracking individual Sectors. On the other hand, by focusing on a more recent time period and limiting the search to a specific sector, one can complete the search quickly and have the freedom to move onto another custom search.
Another feature worth mentioning is that a OneClick Search provides the ability to evaluate "Alternate Data". This can be a much more efficient approach than simply running against one big Evaluation Period. For example, let's say we ran against 20 years of data in our first OneClick Search. Every combination that was run was required to evaluate all 20 years of data, and this was quite slow. But let's say in the second OneClick Search, we broke it up so that our main search was only the most recent 10 years, but we had an Alternate Data evaluation for the 10 prior years. In this case, the initial 10 year period is evaluated, and only if that period passes the test will the prior 10 years be evaluated. This multi-level approach helps make the search much more efficient.
Sorry for the long answer. But, put simply, we haven't lifted the restriction because the demand hasn't been very high to do so. Most users looking to evaluate larger time frames might be doing it via multiple layers, as mentioned.
Feel free to ask if you have additional questions or comments on this.
Pete