Wing should present a responsive, snappy user interface even on relatively slow hardware. In some cases, Wing may appear sluggish:
- 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.
- If you are working on a multi-core virtual machine and 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.0 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.0\bin\wing.exe" on Windows. Although Wing runs on only one core, this technique has been reported to improve performance.
|« 18.2. Obtaining Diagnostic Output||Table of Contents||18.4. Failure to Detect HTTP Proxy and Connect to wingware.com »|