From: Tom Shelton on 3 Oct 2009 11:56 On 2009-10-03, Schmidt <sss(a)online.de> wrote: > > "Mike Williams" <Mike(a)WhiskyAndCoke.com> schrieb im Newsbeitrag > news:eeSHPZCRKHA.488(a)TK2MSFTNGP05.phx.gbl... > >> Your calculations seems to be spot on there, ... >> VB6: >> MT: 1.32 sec >> ST: 2.66 sec > > Well, it's hardware <g> ... > Somewhat more predictable that. > >> The only reason I can think of why Tom Shelton's dual core is >> not scaling linearly between running single or multi thread is >> perhaps when running your code he has some background >> task running which is using a fair amount of processor time? > > Now, what could that be then... ;-) > > No (bad joke), ...seriously - the only other reason I can think of > is - (assuming Tom was testing the new compile with the timer- > decoupled GDI-drawingcode and *not* commented that out) - Yes. > that Toms machine is doing exceptionally bad with regards to > any final rendering to the screen (GDI also affected a bit, > not only GDI+) - the about 60 Refreshs per second are far > less than the former ones (which were done on each incoming line), > but if the MT-code runs about 1.8 seconds on Toms machine, > then there are however about 110 Screen-Refresh "on todo" > which definitely make some percentage in the calculation. > But how many percentpoints, depends on the graphics- > subsystem, if that can render hardware-based (usually the case) - > or not. > I can't comment on this. I'm not a graphics expert. The video card is a NVIDIA GeForce 8600 GT. > Another reason could be that Tom is running the VB6- > version in a VM (though on the same hardware) - not > likely - just to be sure...? > No way. I only used the vm to compile the code when I was attempting to disable drawing. The executable has always been run on my Vista desktop. > Maybe Karl - or someone else could take an additional > run again with the new MBSet.zip, to verify our both results > on hardware with a "normally" working graphics-subsystem > (at least, that the new version should scale with nearly > factor 2 between single- and multithreaded, even with > activated GDI-Refreshs). I never posted the st numbers. I only posted mt numbers. the numbers I posted was three runs, mt. -- Tom Shelton
From: Tom Shelton on 3 Oct 2009 11:56 On 2009-10-03, Mike Williams <Mike(a)WhiskyAndCoke.com> wrote: > "Schmidt" <sss(a)online.de> wrote in message > news:%23A2QY6CRKHA.220(a)TK2MSFTNGP02.phx.gbl... > >> But how many percentpoints, depends on the graphics- >> subsystem, if that can render hardware-based (usually >> the case) - or not. > > I think that Tom is running Vista, which means that he almost certainly > won't be getting any GDI hardware acceleration. I am running vista. -- Tom Shelton
From: Mike Williams on 3 Oct 2009 13:11 "Tom Shelton" <tom_shelton(a)comcastXXXXXXX.net> wrote in message news:uypIhIERKHA.488(a)TK2MSFTNGP05.phx.gbl... > I am running vista. Well in that case you almost certainly won't be getting any GDI hardware acceleration either from VB.Net or from VB6. In fact if you right click your desktop and select Personalize (how I hate those zzzz's!) and then select Display Settings and click the Advanced Settings button and click the Troubleshoot tab you'll see a button called Change Settings. However, that button will almost certainly be greyed out and underneath it you will see a message to the effect, "Your current display driver does not allow changes to be made to hardware acceleration settings". That's Micro$speak for, "Vista has crippled you hardware acceleration and so there is nothing to change!". This button by the way was for people who in XP and below were having trouble with some very old or badly written programs which might not work properly under hardware acceleration, and so the troubleshooting tab gave you the opportunity of temporarily switching it off. It is possible to get the hardware acceleration back, but it requires you to find and install a suitable XP video card driver in your Vista setup, ignoring all the dire warnings when you do so, and then perform a restart (although this might not work with all setups). However, this will totally remove all your fancy Vista desktop stuff and you will effectively be back to an XP desktop and you will remain so permanently, or at least until you reinstall your Vista video card driver. Just as a matter of interest, I've heard that Micro$oft have had a change of heart and have brought back GDI acceleration in Windows7, but I can't confirm it because I haven't tried Windows 7 myself and I am extremely unlikely ever to do so until I eventually buy another machine many years down the line, by which time it will probably be Windows9.3 and all rendering will have to be done over a micropayment per scanline network;-) Mike
From: Tom Shelton on 3 Oct 2009 14:12 On 2009-10-03, Mike Williams <Mike(a)WhiskyAndCoke.com> wrote: > "Tom Shelton" <tom_shelton(a)comcastXXXXXXX.net> wrote in message > news:uypIhIERKHA.488(a)TK2MSFTNGP05.phx.gbl... > >> I am running vista. > > Well in that case you almost certainly won't be getting any GDI hardware > acceleration either from VB.Net or from VB6. In fact if you right click your > desktop and select Personalize (how I hate those zzzz's!) and then select > Display Settings and click the Advanced Settings button and click the > Troubleshoot tab you'll see a button called Change Settings. However, that > button will almost certainly be greyed out and underneath it you will see a > message to the effect, "Your current display driver does not allow changes > to be made to hardware acceleration settings". That's Micro$speak for, > "Vista has crippled you hardware acceleration and so there is nothing to > change!". This button by the way was for people who in XP and below were > having trouble with some very old or badly written programs which might not > work properly under hardware acceleration, and so the troubleshooting tab > gave you the opportunity of temporarily switching it off. > > It is possible to get the hardware acceleration back, but it requires you to > find and install a suitable XP video card driver in your Vista setup, > ignoring all the dire warnings when you do so, and then perform a restart > (although this might not work with all setups). However, this will totally > remove all your fancy Vista desktop stuff and you will effectively be back > to an XP desktop and you will remain so permanently, or at least until you > reinstall your Vista video card driver. Just as a matter of interest, I've > heard that Micro$oft have had a change of heart and have brought back GDI > acceleration in Windows7, but I can't confirm it because I haven't tried > Windows 7 myself and I am extremely unlikely ever to do so until I > eventually buy another machine many years down the line, by which time it > will probably be Windows9.3 and all rendering will have to be done over a > micropayment per scanline network;-) > > Mike The same button is greyed out in Win7 64-bit, and I don't get virtually identical timings. -- Tom Shelton
From: Tom Shelton on 3 Oct 2009 14:13
On 2009-10-03, Tom Shelton <tom_shelton(a)comcastXXXXXXX.net> wrote: > On 2009-10-03, Mike Williams <Mike(a)WhiskyAndCoke.com> wrote: >> "Tom Shelton" <tom_shelton(a)comcastXXXXXXX.net> wrote in message >> news:uypIhIERKHA.488(a)TK2MSFTNGP05.phx.gbl... >> >>> I am running vista. >> >> Well in that case you almost certainly won't be getting any GDI hardware >> acceleration either from VB.Net or from VB6. In fact if you right click your >> desktop and select Personalize (how I hate those zzzz's!) and then select >> Display Settings and click the Advanced Settings button and click the >> Troubleshoot tab you'll see a button called Change Settings. However, that >> button will almost certainly be greyed out and underneath it you will see a >> message to the effect, "Your current display driver does not allow changes >> to be made to hardware acceleration settings". That's Micro$speak for, >> "Vista has crippled you hardware acceleration and so there is nothing to >> change!". This button by the way was for people who in XP and below were >> having trouble with some very old or badly written programs which might not >> work properly under hardware acceleration, and so the troubleshooting tab >> gave you the opportunity of temporarily switching it off. >> >> It is possible to get the hardware acceleration back, but it requires you to >> find and install a suitable XP video card driver in your Vista setup, >> ignoring all the dire warnings when you do so, and then perform a restart >> (although this might not work with all setups). However, this will totally >> remove all your fancy Vista desktop stuff and you will effectively be back >> to an XP desktop and you will remain so permanently, or at least until you >> reinstall your Vista video card driver. Just as a matter of interest, I've >> heard that Micro$oft have had a change of heart and have brought back GDI >> acceleration in Windows7, but I can't confirm it because I haven't tried >> Windows 7 myself and I am extremely unlikely ever to do so until I >> eventually buy another machine many years down the line, by which time it >> will probably be Windows9.3 and all rendering will have to be done over a >> micropayment per scanline network;-) >> >> Mike > LOL... Should be: > The same button is greyed out in Win7 64-bit, and I get virtually > identical timings. This is on the same hardware by the way - tripple boot system :) -- Tom Shelton |