p2p.wrox.com Forums

Need to download code?

View our list of code downloads.


  Return to Index  

comdeveloper thread: How to using shared memory in COM!


Message #1 by "NingYang" <ningyang@s...> on Tue, 27 Feb 2001 03:07:36
Hi everybody.

I design a COM component and put it in the MTS.It has a method to use a 

configration file to complete it's task.

the method must open the configration file many times, I think it could be 

very slowly.I want to put the configration file into memory.

The question is: when component is deactiveted it must release the share 

memory,another call to the same component will recreated the share memory, 

the created process is also slowly.Do you have any good ideas or 

suggestion.Hope you help.

I an not good at English but wish someone to understand me.

Message #2 by klescgl@N... on Tue, 27 Feb 2001 08:35:54 -0500
Morning,



We use a similar mechanism here, and with the server modification to

Win2000 and COM+ from NT4 and MTS, we found that the performance hit for

reading the file from disk and reading the data from shared RAM is roughly

equivalent because NTFS caches frequently used files. You may not want to

manually cache the data.



HTH...

Gary Klesczewski











"NingYang" <ningyang@s...>





02/26/2001 10:07 PM



Please respond to "COMdeveloper" <comdeveloper@p...>





To:   "COMdeveloper" <comdeveloper@p...>

cc:    (bcc: Gary L. Klesczewski/NUS)

Subject:  How to using shared memory in COM!







Hi everybody.

I design a COM component and put it in the MTS.It has a method to use a

configration file to complete it's task.

the method must open the configration file many times, I think it could be

very slowly.I want to put the configration file into memory.

The question is: when component is deactiveted it must release the share

memory,another call to the same component will recreated the share memory,

the created process is also slowly.Do you have any good ideas or

suggestion.Hope you help.

I an not good at English but wish someone to understand me.








  Return to Index