Wing should present a responsive, snappy user interface even on relatively slow hardware. In some cases, Wing may appear sluggish:
- Try using a different Display Theme from preferences -- the pixmap manipulations in Wing's default themes sometimes fail to be accelerated on certain display hardware. Oddly, this seems worse on faster hardware than on slower hardware.
- If you have nVidia desktop manager, disable it for Wing.
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.
- In wxPython and other code that uses from xxx import * style imports, the auto-completer may initially be slow to appear if it needs to process many hundreds of symbols. This should only happen the first time it appears, however.
- On Windows, if Wing is started while operating via Remote Desktop Connection, performance is terrible, even after quitting the RDC session and working directly on the machine that is running Wing. However, if Wing is started on the machine on which it runs, performance is very lively on that machine and acceptable if switched to operating via RDC without quitting Wing.
- If you are displaying Wing remotely via X11, try turning off anti-aliased fonts by placing this file in ~/.fonts.conf on the display machine and then restarting the X server.
- 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 wing4.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 4.1\bin\wing.exe" on Windows. Although Wing runs on only one core, this technique has been reported to improve performance.
|« 18.4. Obtaining Diagnostic Output||Table of Contents||18.6. Failure to Detect HTTP Proxy and Connect to wingware.com »|