Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs
Please explain the following sentence: 'Use exceptions where you really need them -- not only do they have high basic cost, but their presence can hurt compiler analysis.'
Just as it can be more difficult for people to read code that has try-catch blocks, it is more difficult for a compiler to analyze such code. In terms of legibility, however, try-catch blocks can actually be beneficial, because they describe the types of problem situations the software is expected to manage and how it is expected to manage them. This mechanism allows you to deal with problems as close to their source as you choose. At runtime, the presence of try-catch blocks doesn't significantly affect performance -- except when an exception occurs. In such situations, however, you must handle the exception anyway, so the cost is tolerable.
Only when the situation is truly exceptional should you use this mechanism, though you may be tempted to throw exceptions simply to take advantage of their control-flow aspects. A good use of this mechanism would be to throw an exception if a file could not be found; a poor use would be to throw an exception with the name of a file that had been found. In the former case, the cost of the mechanism would only be incurred when the app was unable to proceed normally; in the latter case the cost would be incurred all the time without any added benefit.