Coming from a SW design and coding background, my guess is that the big difference between PT11 and PT12 is threading management (which drives CPU core management). Watching CPU core loading in Win 7's Task Manager | Performance or Win 8's Task Manager | Resource Monitor | CPU (I assume there is a Mac OS equivalent), I see a very different picture in PT12 vs. PT11. Threading in the app talks to core mgmt and the scheduler in the OS kernel. Broadly speaking, threading mgmt is pervasive in an app and generally requires a total redesign of a non-"multi-core aware" app, so I doubt that PT11 will get the threading mgmt improvements I see in PT12, since it would mean a very major rewrite of PT11. So, my conclusion is the major "gap" between PT11 and PT12 is "core awareness" and threading mgmt, i.e., that PT12 is PT11 redesigned to optimize threading mgmt. PT11 went to 64 bit, but didn't improve threading mgmt. PT12 has the threading mgmt that .... missed the ship deadline for PT11?? (Am I being too Dilbert here?). A corollary to this premise is that retro-compatibility (think blue I/O) missing in PT12 that was in PT11 arose from a decision not to redesign elements required for retro-compatibility.
Watch the core loading in PT12 vs PT11 when launching a large session with high plugin and VI counts.
Watch the core loading in PT12 vs PT11 when launching a large session with high plugin and VI counts.
Aucun commentaire:
Enregistrer un commentaire