|
|
You're in the
dotnet xml
group:How to keep XSLs in Memory?
dotnet xml:
I'm working on a project that uses over a hundred XLSs for transforming xml documents. The project consists of several webservices (IIS) calling a few dlls. This dlls make the business logic and are the ones that do the transformation, so the XLSs are used by these dlls. Right now we have the XSLs files on hard disk. This means there is lots of reading from disk. Since reading from disk is much slower than reading from memory I am looking for a way to keep them in memory. Any Ideas? Will IIS cache them? How? (Keep in mind they are used by the dlls) I also was thinking simple work around. Using a RAM Disk, but it seems Windows 2003 server does not support RAM Disks. Any help? Thanks.
Thanks Oleg
Can you tell me how to cache the XslTransform? Can you send me sample code of the first call that do the cache and the other calls that will use the cache objets.? Thanks again Alexis [quoted text, click to view] "Oleg Tkachenko [MVP]" wrote:
> Alexis wrote: > > > I'm working on a project that uses over a hundred XLSs for transforming xml > > documents. The project consists of several webservices (IIS) calling a few > > dlls. This dlls make the business logic and are the ones that do the > > transformation, so the XLSs are used by these dlls. Right now we have the > > XSLs files on hard disk. This means there is lots of reading from disk. Since > > reading from disk is much slower than reading from memory I am looking for a > > way to keep them in memory. > > Any Ideas? > > Will IIS cache them? How? (Keep in mind they are used by the dlls) > > > > I also was thinking simple work around. Using a RAM Disk, but it seems > > Windows 2003 server does not support RAM Disks. > > Just cache loaded XslTransform objects in cache instead of loading them > for each request. XslTransform.Transform() method is thread-safe, so > once XslTransaform object is created and Load() method has been called, > it's safe to run Transform() method in many threads. > > -- > Oleg Tkachenko [XML MVP, MCP] > http://blog.tkachenko.com
Thanks again.
I read the article but they are using the Application object to store the cached objects. But as I said in the first question the transformation is done by a Dll so I don't have access to the Application Object there. Do you know of a method of caching without using the Application object? More specific caching from a Dll. You can read again the first question to understand better the problem I am having. Thanks again. [quoted text, click to view] "Oleg Tkachenko [MVP]" wrote:
> Alexis wrote: > > > Can you tell me how to cache the XslTransform? > > Can you send me sample code of the first call that do the cache and the > > other calls that will use the cache objets.? > > If you are talking about ASP.NET, you can use standard caching methods. > Take a look at > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scalenetchapt09.asp > for a sample. > > -- > Oleg Tkachenko [XML MVP, MCP] > http://blog.tkachenko.com
[quoted text, click to view]
On Mon, 21 Mar 2005 06:59:04 -0800, Alexis wrote: > I also was thinking simple work around. Using a RAM Disk, but it seems > Windows 2003 server does not support RAM Disks. There's no RAM disk driver *shipped* with Windows 2000 and above, but there are many third-party RAM disk drivers available that will work. Seek (on
[quoted text, click to view]
Alexis wrote: > I'm working on a project that uses over a hundred XLSs for transforming xml > documents. The project consists of several webservices (IIS) calling a few > dlls. This dlls make the business logic and are the ones that do the > transformation, so the XLSs are used by these dlls. Right now we have the > XSLs files on hard disk. This means there is lots of reading from disk. Since > reading from disk is much slower than reading from memory I am looking for a > way to keep them in memory. > Any Ideas? > Will IIS cache them? How? (Keep in mind they are used by the dlls) > > I also was thinking simple work around. Using a RAM Disk, but it seems > Windows 2003 server does not support RAM Disks. Just cache loaded XslTransform objects in cache instead of loading them for each request. XslTransform.Transform() method is thread-safe, so once XslTransaform object is created and Load() method has been called, it's safe to run Transform() method in many threads. -- Oleg Tkachenko [XML MVP, MCP]
[quoted text, click to view]
On Tue, 22 Mar 2005 09:37:04 -0800, Alexis wrote: > But as I said in the first question the transformation is > done by a Dll so I don't have access to the Application Object there. Your original post said the DLL will be called by a web service. So there ultimately is an Application object available, which your DLL can access with this: HttpContext.Current.ApplicationInstance Or, if you don't mind if your XSL objects are occasionally flushed from the cache and will be reloaded, you can make more direct use of the ASP.NET Cache this way:
[quoted text, click to view]
Alexis wrote: > Can you tell me how to cache the XslTransform? > Can you send me sample code of the first call that do the cache and the > other calls that will use the cache objets.? If you are talking about ASP.NET, you can use standard caching methods. Take a look at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scalenetchapt09.asp for a sample. -- Oleg Tkachenko [XML MVP, MCP]
[quoted text, click to view]
Alexis wrote: > I read the article but they are using the Application object to store the > cached objects. But as I said in the first question the transformation is > done by a Dll so I don't have access to the Application Object there. > > Do you know of a method of caching without using the Application object? Quick and dirty cache is just plain Hashtable. You can make it better using WeakReferences. Otherwise take a look at the "Caching Application Block" http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/caching1.asp -- Oleg Tkachenko [XML MVP, MCP]
Oleg Thanks again I really appreciate your help
But you are getting me to nowhere. Graet book index but little contect. Thanks anyway for trying. [quoted text, click to view] "Oleg Tkachenko [MVP]" wrote:
> Alexis wrote: > > > I read the article but they are using the Application object to store the > > cached objects. But as I said in the first question the transformation is > > done by a Dll so I don't have access to the Application Object there. > > > > Do you know of a method of caching without using the Application object? > > Quick and dirty cache is just plain Hashtable. You can make it better > using WeakReferences. > Otherwise take a look at the "Caching Application Block" > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/caching1.asp > > -- > Oleg Tkachenko [XML MVP, MCP] > http://blog.tkachenko.com
Ross Thankyou very much.
I have not have time to try it yet but it make a lot of sense. I was just wondering how efficient it may be. The whole purpose of keeping the XSL files or objects in memory is to improve performance. Do you know if accessing the HttpContext from a dll will have some impact on performance? Thanks a lot again I really appreciate your help. [quoted text, click to view] "Ross Presser" wrote:
> On Tue, 22 Mar 2005 09:37:04 -0800, Alexis wrote: > > > But as I said in the first question the transformation is > > done by a Dll so I don't have access to the Application Object there. > > Your original post said the DLL will be called by a web service. So there > ultimately is an Application object available, which your DLL can access > with this: > > HttpContext.Current.ApplicationInstance > > Or, if you don't mind if your XSL objects are occasionally flushed from the > cache and will be reloaded, you can make more direct use of the ASP.NET > Cache this way: > > HttpContext.Current.Cache
I am not really a fan of using third-party software but thanks any way for
the tip. [quoted text, click to view] "Ross Presser" wrote:
> On Mon, 21 Mar 2005 06:59:04 -0800, Alexis wrote: > > > I also was thinking simple work around. Using a RAM Disk, but it seems > > Windows 2003 server does not support RAM Disks. > > There's no RAM disk driver *shipped* with Windows 2000 and above, but there > are many third-party RAM disk drivers available that will work. Seek (on > Google) and ye shall find.
[quoted text, click to view]
On Thu, 24 Mar 2005 07:07:03 -0800, Alexis wrote: > I have not have time to try it yet but it make a lot of sense. I was just > wondering how efficient it may be. The whole purpose of keeping the XSL files > or objects in memory is to improve performance. Do you know if accessing the > HttpContext from a dll will have some impact on performance? Well, the thing of it is, where do you expect the DLL to cache it? You need something that has persistence between invocations of your DLL, and the easiest answer to that is to let ASP.NET handle it. And the way to access ASP.NET's cache is through HttpContext.Current. I could be wrong about this, and you might want to check the other dotnet
What I want to keep in memory are XSLs files used for transformation not the
data so the contenct don't change, but I don't think ASP.NET will cache XSL files. See my original goal is to keep XSL files in memory instead of having to read them from disk on every request [quoted text, click to view] "Ross Presser" wrote:
> On Thu, 24 Mar 2005 07:07:03 -0800, Alexis wrote: > > > I have not have time to try it yet but it make a lot of sense. I was just > > wondering how efficient it may be. The whole purpose of keeping the XSL files > > or objects in memory is to improve performance. Do you know if accessing the > > HttpContext from a dll will have some impact on performance? > > Well, the thing of it is, where do you expect the DLL to cache it? You need > something that has persistence between invocations of your DLL, and the > easiest answer to that is to let ASP.NET handle it. And the way to access > ASP.NET's cache is through HttpContext.Current. > > I could be wrong about this, and you might want to check the other dotnet > newsgroups for a more informed opinion.
[quoted text, click to view]
On Fri, 25 Mar 2005 07:27:03 -0800, Alexis wrote: > What I want to keep in memory are XSLs files used for transformation not the > data so the contenct don't change, but I don't think ASP.NET will cache XSL > files. See my original goal is to keep XSL files in memory instead of having > to read them from disk on every request ASP.NET's Application object, or Cache object, will cache ANY object, with
I would like to try to cache the xsl objects them.
Can you provide me with a code sample? I have not used cahing in yet. [quoted text, click to view] "Ross Presser" wrote:
> On Fri, 25 Mar 2005 07:27:03 -0800, Alexis wrote: > > > What I want to keep in memory are XSLs files used for transformation not the > > data so the contenct don't change, but I don't think ASP.NET will cache XSL > > files. See my original goal is to keep XSL files in memory instead of having > > to read them from disk on every request > > ASP.NET's Application object, or Cache object, will cache ANY object, with > whatever expiration/retention rules you care to set up.
[quoted text, click to view]
On Wed, 30 Mar 2005 07:05:07 -0800, Alexis wrote: > I would like to try to cache the xsl objects them. > Can you provide me with a code sample? I have not used cahing in yet. > Hope you don't mind VB.NET ... ' this function will look in the ASP.NET cache for an XSLTransform; ' if it's there, it will return it; ' if it's not, it will call CreateTheXSLT() to create it. Public Function GetXSLTObject(ByVal key As String) _ As System.Xml.Xsl.XslTransform ' get a handle to the ASP.NET cache Dim c As Web.Caching.Cache c = HttpContext.Current.Cache Dim x As System.Xml.Xsl.XslTransform If c.Item(key) Is Nothing Then ' it wasn't in the cache ... ' create it fresh, then put it in the cache x = CreateTheXSLT(key) ' sliding expiration of 2 hrs ... ' if we don't use it for 2 hrs, ASP.NET is allowed to ' purge it from the cache c.Add(key, x, Nothing, Nothing, _ System.TimeSpan.FromHours(2), _ Caching.CacheItemPriority.Normal, _ Nothing) Return x Else ' yaay, it was in the cache ... return it x = c.Item(key) Return x End If
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |