Flash Is Slow/Crashes? How can I OVERCLOCK Flash?

Question

This is clearly not an isolated problem as multiple similar inquiries have already been made on this topic:
http://forums.adobe.com/message/5577432#5577432
http://forums.adobe.com/thread/933530
http://forums.adobe.com/message/3722411#3722411
Moreover, you always hear users of Flash jokingly (and sometimes not so jokingly) complain about how Flash is slow and/or crashes all the time.
While sometimes this is attributable to memory and CPU of the computer, often times it's not.
This is one of those times it's NOT.
(Using Adobe CS6 Flashx64 in WIndows 8; working on relatively large animation file.
1.Have set priortiy as high as possibly can (Realtime),
2.Set Publish Cache preferences to:
        4600MB for Disk cache size limit
        4600MB for Memory-cache size limit, and
        4600MB for Maximum size for memory cache entry).
   (yes, I'm serious about the whole overclocking thing)
However, Flash sometimes slows down/crash when importing huge symbol from one flash file to another, during playback, for .swf creation, etc.
My CPU remains at an annoying low of 21% used and high of 3.0/7.9 GB during Flash's most intense (aka slow) moments, so it can't be due to that, I think?
As side, I'd like to try to make this thread the default go-to for people who are tired of Flash crashing and just want to set everything up so that if Flash is laggy and crashes, it will only be because of computer limits (not enough RAM or CPU) as opposed to any other junk (like arbitrary Cache limits on program or file or something, .fla is crazy big).
So any and all Flash optimization tips (including changing Windows settings) welcome!

Answer 1

this is from a chapter on optimizing flash performance in:  http://www.amazon.com/Flash-Game-Development-Social-Mobile/dp/1435460200/ref=sr_1_1?ie=UTF 8&qid=1376401848&sr=8-1&keywords=gladstien
Easiest to Hardest to Implement
Do not use Filters.
Always use reverse for-loops and avoid do-loops and avoid while-loops.
Explicitly stop Timers to ready them for gc (garbage collection).
Use weak event listeners and remove listeners.
Strictly type variables whenever possible.
Explicitly disable mouse interactivity when mouse interactivity not needed.
Replace dispatchEvents with callback functions whenever possible.
Stop Sounds to enable Sounds and SoundChannels to be gc'd.
Use the most basic DisplayObject needed.
Always use cacheAsBitmap and cacheAsBitmapMatrix with air apps (i.e., mobile devices).
Reuse Objects whenever possible.
Event.ENTER_FRAME loops: Use different listeners and different listener functions applied to as few DisplayObjects as possible.
Pool Objects instead of creating and gc'ing Objects.
Use partial blitting.
Use stage blitting.
Use Stage3D.
Greatest to Least Benefit
Use stage blitting (if there is enough system memory).
Use Stage3D.
Use partial blitting.
Use cacheAsBitmap and cacheAsBitmapMatrix with mobile devices.
Explicitly disable mouse interactivity when mouse interactivity not needed.
Do not use Filters.
Use the most basic DisplayObject needed.
Reuse Objects whenever possible.
Event.ENTER_FRAME loops: Use different listeners and different listener functions applied to as few DisplayObjects as possible.
Use reverse for-loops and avoid do-loops and while-loops.
Pool Objects instead of creating and gc'ing Objects.
Strictly type variables whenever possible.
Use weak event listeners and remove listeners.
Replace dispatchEvents with callback functions whenever possible.
Explicitly stop Timers to ready for gc.
Stop Sounds to enable Sounds and SoundChannels to be gc'd.