[MetaCRS] Re: RFC #5 -- Multi-thread upgrade
Paul Nalos
paul.nalos at safe.com
Thu Jul 21 19:59:44 EDT 2011
Hi Hugues, MetaCRS,
I've taken the time to consult with other stakeholders at Safe Software.
> Just curious, what's acceptable for you? How much memory is acceptable?
We don't have a specific limit in mind. While it would be nice if the
new behavior was configurable, we don't expect to be adversely
affected even if CS-MAP fully cached every grid it loaded.
Regards,
Paul
On Mon, Jul 18, 2011 at 4:26 AM, Hugues Wisniewski
<hugues.wisniewski at autodesk.com> wrote:
>
> Hello Paul,
>
> > I haven't spent much time with MapGuide, but I took a look at the
> > source and architecture document, and my understanding is that there
> > is a single server process with multiple worker threads. Calls to
> > CS-MAP are protected by a critical section. (I hope that's efficient
> > given there is one call per point when a datum shift is in play.) If
> > this is the case, there would only be one copy of each grid in memory,
> > which sounds Ok to me.
>
> You're correct on this. The question is how many users can we have at the same time. My understanding is hundreds, possibly more than a thousand but I'm not 100% sure. Just curious, what's acceptable for you? How much memory is acceptable?
> Concerning the critical section in MapGuide, an RFC is coming up for review very soon to take advantage of the CS-Map RFC we're discussing here and remove the critical sections for the CS-Map transformations that are re-entrant.
>
> > My sense is that all of these issues could be overcome through
> > additional effort and engineering (e.g., make the full-grid-caching...
>
> You're right.
> This has also been investigated but has to be pushed back because there's currently no bandwidth to support this additional engineering effort.
>
> Thanks for your detailed input
>
> Hugues
More information about the MetaCRS
mailing list