[ffcmike]

I don't consider myself to be knowledgeable about how these things work, but it seems like certain things don't add up and so I'm seeking some further clarification.

One of the more commonly mentioned advantages to the new client is reduced lag, I understand that displays have been largely over-hauled, so I didn't really expect an improvement on script time which I'd guess isn't really possible to much extent anyway.

Sure enough when I test script time via showscriptstats and /clientstats within RC, systems are taking a higher percentage of resources in the V6 client.
I've considered the possibility that there may be new processes that might lead to a visible increase on display related script times, but ultimately be speeding things up in the background. However when I check CPU usage of the entire client via windows task manager this is also a higher number in V6 compared to V5.

One possibility I've considered is that the current beta client could possibly contain alot of consuming debug processes which would be removed with the real thing, another possibility is that the new built-in optimisations of displays are rendering the optimisations of displays within Classic's custom systems un-necessary.
A common example of this optimisation would be the storing of display objects, then simply modifying the objects x, y, text and colors whenever there's a related change from the relevant player, as opposed to creating a new display each frame.
Another thought is simply that script time is being sacrificed to save on a different form of resource.

Another thing I'm somewhat confused about is that I've read directX has been phased out of the new client, with opengl now being some form of default.
When I open the client normally to test usage I'm getting a significantly higher percentage compared to when I am deliberately opening the client via shortcut with "-opengl" at the end of the target.
There may be a good explanation for this but it goes against my current understanding.