Ya...thanks ;)
Jim
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, September 10, 2001 11:23 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Sanity Check - Memory Footprint of compiled Stylesheet
>
>
>
> Well, if you're measuing debug memory footprint, then it will
> always be
> bad. Microsoft's run-time has all sorts of memory debugging
> stuff that
> will really push up usage. You should never use the debug
> build to measure
> anything related to memory usage or performance.
>
> Dave
>
>
>
>
>
> "Murphy, James"
>
> <James.Murphy@exc To:
> "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> elergy.com> cc:
> (bcc: David N Bertoni/CAM/Lotus)
> Subject: RE:
> Sanity Check - Memory Footprint of compiled Stylesheet
> 09/10/2001 11:03
>
> AM
>
> Please respond to
>
> xalan-dev
>
>
>
>
>
>
>
>
> Thanks Dave, fair enough we can wait patiently )or even help
> out?!) for
> this
> to become a reality. It will be an issue for us in the near
> future but
> lucky for us it isn't as bad in optimized builds. 25 MB -
> shrinks to 12
> MB...
>
> Jim
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, September 10, 2001 10:20 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: Sanity Check - Memory Footprint of compiled Stylesheet
> >
> >
> >
> > It wouldn't surprise me that this is the case. Pretty much
> > everything in a
> > stylesheet will end up as an object. We haven't optimized
> > the allocation
> > for stylesheet objects like we've optimized for the DOM
> > because there have
> > been very few situations where this has become an issue.
> >
> > We'll eventually get around to working on this, but I'm not
> > sure when it
> > will happen.
> >
> > Dave
> >
> >
> >
> >
> >
> > "Murphy, James"
> >
> > <James.Murphy@exc To:
> > "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> > elergy.com> cc:
> > (bcc: David N Bertoni/CAM/Lotus)
> > Subject: RE:
> > Sanity Check - Memory Footprint of compiled Stylesheet
> > 09/08/2001 10:39
> >
> > AM
> >
> > Please respond to
> >
> > xalan-dev
> >
> >
> >
> >
> >
> >
> >
> >
> > Any sane people out there? I am still having issues with this...
> > Jim
> >
> > > -----Original Message-----
> > > From: Murphy, James [mailto:[EMAIL PROTECTED]]
> > > Sent: Friday, September 07, 2001 11:41 AM
> > > To: '[EMAIL PROTECTED]'
> > > Subject: Sanity Check - Memory Footprint of compiled Stylesheet
> > >
> > >
> > > Hi Xalan List
> > >
> > > I wanted to make sure I'm still insane :-0
> > >
> > > I have a stylesheet that includes a bunch of other
> > > stylesheets - total size
> > > of all XSL is about 1 MB on disk. When I parse the thing
> > > using Xerces-1.5
> > > into a compiled style (based on compiledstylesheet sample) my
> > > application
> > > footprint grows by 25 MB! I thought this was a little much
> > and could
> > > prevent us from using compiled stylesheets since we may have
> > > dozens active
> > > at anyone time. I am using the XercesParserLiason with
> Xerces, as I
> > > mentioned. Is this normal or is there something I can so to
> > > trim this down
> > > a bit? I'm hip tot he time/space tradeoff and really love
> > > the performance
> > > gains we see. But I wonder about our ability to scale
> out with more
> > > stylesheets.
> > >
> > > Thanks
> > > Jim
> > >
> > > BTW, is there a searchable archive for this list?
> > >
> >
> >
> >
> >
>
>
>
>
