Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Object Creation Under Windows NT4 and Windows 2000 : Page 3

Do you have an application which is running sluggishly under Windows NT4 / MTS, not providing quite the performance you expect? Are you thinking about porting it to Windows 2000 / COM+ in order to achieve a performance boost? Be very careful. Depending on why your application is not performing up to speed under NT4, you may not experience any performance gain by migrating to Win2K. You might very well see a performance drop. A significant performance drop. In this article Joseph Geretz will show you all the do's and don'ts of the subtle art of object creation under Windows NT and 2000.




Building the Right Environment to Support AI, Machine Learning and Deep Learning


Wow! Do you see what I see? Under Windows 2000, using the Library defaults (that is, the defaults which are pre-set by creating a Library application and dragging in the CCBench DLL) object creation takes 33 times longer than it does under NT4 in a Library Package! Now it is true that we were able to optimize the Win2K Library scenario and see quite an improvement as shown below. We adjusted the following declarative settings in an attempt to minimize object creation and access overhead. At the package level, set the security level to perform access checks only at the process level. At the component level, for all three components, disable transaction support, disable JIT, remove support for events and statistics, and disable synchronization support. Then for the Obj and ObjCol objects, specify that they must be activated in the caller’s context (colocation). The ObjWrapper component cannot be colocated since its caller is outside of the COM+ application. After applying these settings we saw the following benchmarks:

W2K, Library Optimized

691 ms

10 ms

20 ms

20 ms

10 ms

Object creation time has improved quite a bit. But still, even under this optimal scenario (which is only possible for non-JIT, non-transactional components), object creation under Win2K took 2

Joseph Geretz is the founder of Focal Point Solutions, Inc., a consulting firm serving clients in the New York metropolitan area. He has been working with Microsoft technologies, developing with VB and COM, since 1994 (back then they called it OLE). His primary focus these days is on N-Tier systems, using Microsoft DNA tools and methodologies. His current language of choice is Visual Basic, although he has fond memories of COBOL, from an earlier, stateless era.
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date