Wing should present a responsive, snappy user interface even on relatively slow hardware. In some cases, Wing may appear sluggish:
With New Projects, the first time you set up a project file, Wing analyzes all source files for the source code browser and auto-completion facilities. During this time, the browser's class-oriented views will display only the source constructs from files of which analysis information has already been obtained. The user interface may also appear to be sluggish and Wing will consume substantial amounts of CPU time.
To avoid this in subsequent sessions, Wing stores its source analysis information to disk in a cache within your User Settings Directory.
On a multi-core virtual machine where Wing runs slowly, you may be able to improve performance by setting the processor affinity for Wing. This is done with schedtool -a 0x1 -e wing5.1 on Linux (the schedtool package needs to be installed if not already present) and with START /AFFINITY 01 "Wing IDE" "C:\Program Files\Wing IDE 5.1\bin\wing.exe" on Windows. Although Wing runs on only one core, this technique has been reported to improve performance.
On OS X Mavericks, certain graphics drivers have a bug that substantially slows down Wing IDE because the OS is incorrectly detecting Wing IDE as inactive. Turning off App Nap has no effect on this, although the bug may be associated with that feature. The work-around is to put the computer to sleep briefly while Wing IDE is already running. Wing should then remain responsive until it is quit.
|« 18.0. Trouble-shooting Failure to Start||Table of Contents||18.2. Trouble-shooting Failure to Debug »|