To improve your experience with OptiPerl, you may want to change some settings depending on your computer's speed and memory. In general, all of OptiPerl's code that affect the editor, like syntax parsing, box & line code, code folding, are optimized for speed in expense of memory, so a system with over 64 MB of RAM is recommended. However all the graphics are drawn lightning fast; many techniques have been used to increase performance.


Options affected by processor speed


The following options are affected from your computer's speed and graphics card. If you notice an unappealing delay in the redrawing of the editor, you may want to disable one or more of them. We recommend disabling in the order given for a smaller trade-off.


1) Disable Font Smoothing in Options / Editor / Font box


Many resources are used for font smoothing (anti-aliasing), especially if you have Windows XP and have selected the "ClearType" font smoothing method in the display properties. So the first thing you should do to greatly increase performance is to disable it. You might need to restart OptiPerl for this to be applied. The default in OptiPerl is disabled under Win 2000 / XP and enabled under Win 98 / Me / Nt since in these versions this does not affect the speed too much.


2) Box & Line coding from Options / Level coding


These also need a lot of resources. We recommend disabling if your processor is under 500 mz.


In most cases doing 1 and 2 above will make the editor extremely fast, even on very slow processors. However if your computer is extremely slow ( < 300mz ), then also do the following:


  • Disable monospace fonts from Options / Editor / Font box
  • Remove code folding from Options / Editor / Code folding
  • Remove Tab lines from Options / Editor / Tab handling
  • Remove Other "cosmetic" options in Options / Editor / Visual
  • Remove Live syntax checking from Options / Error testing
  • For very slow processors, remove color syntax coding, from Options / Syntax coding


A good test to see how fast the editor redraws, is to open a large script, and then scroll through it by holding down the Page Up or Down buttons.


More performance options


Under Options / Environment II / Performance options, there are some options that also affect performance:


  • Error check delay. Delay time in milliseconds of keyboard inactivity before the automatic error checking initiates (default 1000 ms = 1 second). Note that while perl is loading and checking the code, you can still edit, since the checking takes place in a low priority thread.


  • Explorer check delay. Delay time in milliseconds of keyboard inactivity before the code is parsed to be used in code explorer, box & line coding and code folding (def. 100 ms = 1/10 second). Note that while the code is being parsed, you can still edit, since updating takes place in a low priority thread.


  • Line & Box lookahead. On each redraw of the editor, how many lines of code forward or backwards of the viewable code should be checked for long boxes or lines. On fast computers, over 800mz, you can increase these numbers to arbitrary large numbers. Note that due to a limitation on windows 98/me systems these numbers have no affect after 3000 lines. On windows nt/2000/xp, this is not a limitation. You can put an opening bracket on line 1 of your code, and if the closing bracket is on line 5000, then a huge line will be drawn from line 1 to line 5000. The defaults are 100 lines for Line coding and 1000 lines for box coding.


Options affected by amount of computers memory


The following options, found in Performance options dialog, have to do with the amount of RAM installed. Increase or decrease to change the memory footprint of Optiperl. We recommend increasing if you have over 256mb installed:


  • Max search results. Maximum results logged in code explorer after a regular expression search or replace (def. 20000 items).
  • Max undo levels. Maximum undo levels when editing (def. 100).





Top  Previous  Next