🚀 go-pugleaf

In article <4591@arccs1.fed.FRB.GOV> m1phm02@fed.frb.gov (Patrick H. McAllister) writes:
>
>By the way, the same calculation done in a 16-bit native OS/2 port runs in about 7 sec. It seems to me that if vendors of compute-intensive software were able to get the same kind of speed-up with native OS/2 applications, it would have a big effect on the Windows vs. OS/2 controversy, whereas relying on WIN-OS2 emulation for the same programs may have the opposite effect. 
>
>I would like to see of we can have some discussion here on the architectural features of these operating environments that produce such dramatic speed differences. At first glance, it would seem that, if any kind of code should display about the same speed under these different environments, it would be a small, floating point-intensive computation like this. 


I am assuming that the 16bit native OS/2 port was running under 1.3 when
it was tested for speed.  If this is so, it may point to the amount
of tiling going on for converting the Win-OS/2 session onto the flat
plane structure.  IBM calls those "thunks" and I assume they apply
to Win Apps under 2.0 as well as 1.3 apps under 2.0