Hi Tomasz,

>From the thread you referenced:

> >>> On Fri, Jul 2, 2010 at 5:47 PM, Rob<sidhartha70@<mailto:sidhartha70@>>
wrote:
> >>>
> >>> Herman,
> >>>
> >>> I don't know what sort of info you intend to pass between
instances...
> >>>
> >>> As for myself, I am sharing some .csv files... not arrays in and of 
> >>> themselves...

I stand on my point.

Please answer with what helps users, not esoteric mechanisms most users can't 
ever use.

Thanks,
Michael



--- In [email protected], Tomasz Janeczko <gro...@...> wrote:
>
>   Hello,
> 
> No, you misread  the question asked.
> 
> The question that I was answering to was " what's the quickest and best way 
> to SHARE THE INFORMATION between instances"
> See: http://finance.groups.yahoo.com/group/amibroker/message/150700
> 
> It is about inter-process communication (IPC) !
> 
> What you are talking about is irrelevant to the question asked. RAM disk is 
> not IPC mechanism.
> 
> Best regards,
> Tomasz Janeczko
> amibroker.com
> 
> On 2010-07-05 21:50, michaels_musings wrote:
> > Hello Tomasz,
> >
> > I believe you misunderstood my answer.  I'm stating that writing a DLL is 
> > not faster for a user* than installing a RAM disk driver application.
> >
> > The thread is about how to speed up AB, not the finer points of whether or 
> > not native memory mapping is faster than an application level interface to 
> > said.  So, from a user stand point, "The absolute quickest way is to use a 
> > RAM drive."
> >
> > I know this is your baby, but please understand, we the user base are here 
> > to get a job done.  And for the majority of us, we wish to do that job in 
> > the most timely and efficient manner possible.
> >
> > I like your product, but please, don't bite people's heads off when they 
> > try to help out.
> >
> > Regards,
> > Michael
> >
> > * I'll even conjecture that 90% of this list wouldn't know how to write a 
> > DLL in the first place.
> >
> >
> > --- In [email protected], Tomasz Janeczko<groups@>  wrote:
> >>    Hello,
> >>
> >> "The absolute quickest way would be to use a RAM drive for your common 
> >> shared files.*
> >>
> >> Memory mapped file *IS* mapped to RAM already therefore putting physical 
> >> file in RAM
> >> actually makes no difference, other than just consuming more memory with 
> >> no benefit.
> >>
> >> You do not understand how Windows works, recommended reading:
> >> http://msdn.microsoft.com/en-us/library/ms810613.aspx
> >>
> >> Best regards,
> >> Tomasz Janeczko
> >> amibroker.com
> >>
> >> On 2010-07-05 19:30, michaels_musings wrote:
> >>> --- In [email protected], Tomasz Janeczko<groups@>   wrote:
> >>>> The quickest way to share lots of data would be memory mapped file, but 
> >>>> for that you would need to write a DLL.
> >>>>
> >>>> Best regards,
> >>>> Tomasz Janeczko
> >>>> amibroker.com
> >>> Naw,
> >>>
> >>> The absolute quickest way would be to use a RAM drive for your common 
> >>> shared files.*
> >>>
> >>> For XP/2000 See: http://www.hardwareanalysis.com/content/topic/7963/
> >>> The very long post by Chris Jepson to understand how to keep a reliable 
> >>> backup.  And the last post by Chris Jepson for specific software and 
> >>> install instructions.
> >>>
> >>> Alternatively Search for, "create ram drive {your version of windows}"
> >>>
> >>> Best,
> >>> Michael
> >>>
> >>> * If your a glutton, and can accept some risk, you can put you entire 
> >>> install of AB and the database you're using on a RAM drive as well.
> >>>
> >
> >
> >
> > ------------------------------------
> >
> > **** IMPORTANT PLEASE READ ****
> > This group is for the discussion between users only.
> > This is *NOT* technical support channel.
> >
> > TO GET TECHNICAL SUPPORT send an e-mail directly to
> > SUPPORT {at} amibroker.com
> >
> > TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at
> > http://www.amibroker.com/feedback/
> > (submissions sent via other channels won't be considered)
> >
> > For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
> > http://www.amibroker.com/devlog/
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>


Reply via email to