Yeah, that's exactly what I mean, sorry. It isn't necessarily that it is slow to operate package control itself, it just seems there is a general lag in ST2. For example, "Ctrl + Shift + P" to trigger package control, when a local file is being edited, is instantaneous. If I try and bring that up in a window with a file open over SSH/FTP, there is an extreme lag until the window is rendered. Now I understand that there will be some performance issues with files over a network, but it's ridiculous at times. This lag is also present in any operation if my focused window is a file across a network. For example, there is at least a 5 second delay before displaying the drop down menu from any of the options on the applications menu. Additionally, if I do not close any SFTP files before trying to close ST2, it locks up and needs to be killed. I know this sounds like a network connectivity issue, but the server is local and this has never been an issue with any other application. It is very odd though because ST2 works seamlessly as long as no network files have been accessed. Are there any good ways to debug or monitor processes of ST2 that may help me diagnose this issue? I would really like to continue using this editor. Thanks again for your time.