First, finalize your program. This will enable the compiler to put a lot of optimizations in - especially if you use ARRAYs. We will provide in the near future a profiling option for Visual Eiffel. This will help you to optimize in the right places. Then, make sure that you compiled everything to native code - not to p-code. Finally, use the profiler and the tuner tool we provide. In extreme cases it can be useful to rewrite the most time critical parts using another, specialized language (for example Fortran for numeric applications).
First, finalize your program. This will enable the compiler to put a lot of optimizations in - especially if you use ARRAYs. We will provide in the near future a profiling option for Visual Eiffel. This will help you to optimize in the right places. Then, make sure that you compiled everything to native code - not to p-code. Finally, use the profiler and the tuner tool we provide.
First, finalize your program. This will enable the compiler to put a lot of optimizations in - especially if you use ARRAYs. We will provide in the near future a profiling option for Visual Eiffel. This will help you to optimize in the right places. Then, make sure that you compiled everything to native code - not to p-code. Finally, use the profiler and the tuner tool we provide. In extreme cases it can be useful to rewrite the most time critical parts using another, specialized language (for example Fortran for numeric applications).
First, finalize your program. This will enable the compiler to put a lot of optimizations in - especially if you use ARRAYs. We will provide in the near future a profiling option for Visual Eiffel. This will help you to optimize in the right places. Then, make sure that you compiled everything to native code - not to p-code. Finally, use the profiler and the tuner tool we provide. In extreme cases it can be useful to rewrite the most time critical parts using another, specialized language (for example Fortran for numeric applications).