Sublime Text 2 hangs on Search and Replace in a large sql dump (3.11Mb). How to temporarily disable plugins?

Question

Code editor

Sublime Text 2, which always "flyed", takes a very long time to open a 3.11 MB sql dump. Just walking along the lines of the file is already slowing down. I tried to do a search and replace (a little more than 5 thousand occurrences of the searched string were found) and the editor tightly hung. At the same time, it uses only 25% of the CPU and 40-60MB of memory (on a machine 16GB of memory and Core i5). Sublime Text itself, like the OS (Windows 7 x64), is installed on an SSD, the file being edited is on it. Previously, I never noticed that the ST slowed down, and even more so hung up. Has anyone experienced similar behavior, or is it basically normal for a file of this size?
There is an idea that the problem may be due to some plugin, then the question is how to temporarily disable all plugins so that after editing this file, the editor is returned to the previous state as quickly as possible, with all plugins and settings.
UPDATE:
1. Sublime Text 2 still can't handle search and replace in large files. Disabling plugins (thanks, niosus ) didn't help.
2. Search and replace turned out to be much easier and faster to do with the * nix utility sed , right on the server via SSH. You don't even need to download the dump to your computer - I took it with wget from the old server, unpacked it, made replacements, and uploaded it to the database. For everything about everything 3 minutes with sed --help. The replacement speed of sed is fantastically fast. Thanks HgeNfor a tip. Using sed:

find dump.sql | xargs sed -i -e s/что_ищем/на_что_меняем/g

Answer 1

Maybe use sed to replace it? And the sublime after restarting and closing heavy files usually ceases to be stupid.
CodeIntel and other auto-completes can do a lot of harm on dumps.

Answer 2

Bulk replay in sublime is one of those things that is very slow. I have not been able to get it to work properly. In the ST3 changelog, they somehow wrote that the replay was accelerated, but I did not notice the difference.
Moreover, there is some kind of "barrier". Let's say, for 1000 records it changes instantly, for 1100 - it hangs tightly.

Answer 3

I once noticed that in sublime 2, searching and replacing large files works much faster if you turn off the regular expression mode.

Answer 4

Faced such a problem. Sublime hung tightly during mass replacement. The solution was found purely by chance. If you first click Find All, and then Replace All, then everything works as it should.