SPEED: VB5 ActiveX DLL vs C++ ATL COM DLL

SPEED: VB5 ActiveX DLL vs C++ ATL COM DLL

Post by Kristopher Nelso » Mon, 24 Aug 1998 04:00:00



Does anyone have any knowledge of speed differences between a compiled
C++ ATL COM DLL and a VB5 ActiveX DLL?  Is the difference negligible
(ie, compared to bandwidth issues, database connection issues, etc)

Pointers to any resources or white papers would be excellent.  Thanks in
advance.

-- Kris

------------------------------------------------------------------------
Kristopher Nelson

http://www.kristopher.com
------------------------------------------------------------------------

 
 
 

1. COM / ActiveX Dll speed issue

Hi,

I recently took a VB6 app and put all the business logic and SQL statements
into an ActiveX .dll, using COM with MTS.  This made the application run
much slower, way too slow to warrant using this new version.  I then
re-created the .dll and included it as a reference in the project, so its
not using MTS and not running remotely.  However, it still runs very slow.
When I first tried it the speed was not that bad, but I made a few minor
changes to the .dll, and re-registered it, changing the name and using the
newer version and now its really slow.  For example, the first form, which
loads about 5 combo boxes with data from recordsets (that I put into arrays
using rs.getrows), takes about 8 seconds instead of 1 or 1.5 to load.

Does anyone have any ideas why this runs so slow, or how I could speed it
up?

Thanks,
Ray

2. Help with JDBC/OCI protocol

3. Problem using Data Link file from ATL COM DLL

4. programming ports?

5. Trouble with interface reference: vb 5 driving C++ 5 atl dll

6. Information about SQL Server Internet Connector

7. ntwdblib.dll vs sqlsrv32.dll (native driver vs ODBC driver)

8. US-TX>>>PL/SQL Designers, HOUSTON<<<Yoh Information Technology

9. Calling a public function in a VB ActiveX DLL from a VC DLL

10. creating normal DLL (no ActiveX dll)??

11. ActiveX Dll in VB5

12. VB DLL reading from ADO and colliding with C++ DLL reading there too (on NT)

13. VB and C++ clients declaring the same ActiveX .dll