Hi

Sorry for the late reply.

Great to see you like it and that you are woundering about implementing it :)

I'm very aware of Rollers use of OSCache (which I'm also familiar with) but memcached works in another way. Let me explain to those of you who have not looked at it; First of all it's distributed memory and second it's not an JAVA applications. In other words you can start memcached on as many servers (where you have free space) as you want and it will act as one huge pile of memory for the application. First of all you end up with the posibillity to have unlimited amount of memory and this is a lightning fast way to cache tings, but another advantage is that the cached objects are moved out of the JAVA VM. JAVA just connects to it and this is a huge bennefit if the JAVA EE server dies (not the entire server). If the JAVA EE server dies all the cached objects will still be in memcached and when the JAVA EE server are up running again it will just have the cached objects there again. It does not need to pul every thing from the DB again, it's just there :) Even if the whole server dies or one of the servers alocating memory to memcached only parts of the cached objects will be lost because it's distributed..

I find this much more interesting in a large scale installation than a static content function, but static content are nice for smaller sites which does not have the access to hardware such as larger installations might have.

Anyway; very nice to see you do find this interesting :)

Just to change topic; I'll be starting to look at a integration of the FCKEditor (http://www.fckeditor.net/) into Roller. I think it should be an easy task to do and a nice start for me to be able to contribute. Is there anybody else looking at this?
This does belong in a new tread...

PS: My last post ended up at the root in the apache incubator archive. If this one does also, what am I doing wrong? I'm just replying to the post I want to reply to and the reply adress is [email protected]

Kind regards
Trygve



From: Allen Gilliland <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: roller-dev <[email protected]>
CC: [EMAIL PROTECTED]
Subject: Re: Sharing some stats
Date: Wed, 24 Aug 2005 14:46:50 -0700

I spent a little time playing with memcached today and I must say that I rather like it. The setup was pretty easy and depending on how we would would want to use it I think this could be a nice little feature.

Rather than bother with trying to integrate this into the backend via hibernate I instead decided to just apply it to the page level cache. There are a number of things in the presentation layer caching setup that I think can be cleaned up to make this easier, but so far it hasn't been too bad.

It seems to me like we probably don't need to use memcached for more than just the presentation level caching, and means we should be able to keep our implementation pretty simple.

thanks for making this suggestion Trygve.

-- Allen


On Thu, 2005-08-18 at 00:52, Trygve Lie wrote:
> Hi
>
> I do not think static content is the way to go. By my experience it will
> introduce a lot of new issues.
> At least if the posibillities of static content is introduced it must be
> able to turn it on or off on different levels (not just on or off at a whole
> site).
>
> But; I would much rather see a implementation with Memcached:
> http://www.danga.com/memcached/
>
> I work in a company which maintains and develops the largest media network
> in Norway and we have a quite large scale CMS running all our media
> services. A time a go we did have the same problem with caching as described
> here. Turning on static caching was not an option for us.
> For us Memcached was the definitive solution to a lot of our performance
> problems.
> Now we can just put in a blade server with a lot of memory if we need more
> cache...
>
> In our network there has been done an implementation of Memcached for
> Hibernate. This would probably work for Roller also. I can see if I can get
> this code awailable for the public....
>
> Trygve
>
>
> >From: Lance Lavandowska <[EMAIL PROTECTED]>
> >Reply-To: [email protected]
> >To: [email protected], [EMAIL PROTECTED]
> >Subject: Re: Sharing some stats
> >Date: Tue, 16 Aug 2005 12:02:33 -0500
> >
> >On 8/16/05, Elias Torres <[EMAIL PROTECTED]> wrote:
> > > Then we could write RewriteRules in Apache that translated these for
> >example:
> > >
> > > http://www.jroller.com/page/fate/Weblog?catname=General into
> > > http://www.jroller.com/static-content/fate/general/index.html
> >
> >Suggestion: write the static version to the user's resource directory:
> >http://www.jroller.com/resources/fate/general/index.html
> >
> >The only problem with this is that it could interfere with the
> >maxDirectorySize admin value (eating up space valuable to the user, so
> >that they cannot upload a file).  Since currently that value only
> >measures against the "base" resource directory for the user
> >(/resources/fate) we can get aroudn this issue for the time being by
> >writing all static content to a subdirectory.  THis stops working
> >if/when we allow the user to create subdirectories.
> >
> >Lance
>
> _________________________________________________________________
> MSN Search http://search.msn.no/ Raskere. Rett på sak. Mer presist.
>


_________________________________________________________________
MSN Messenger http://www.msn.no/messenger Den enkleste og raskeste måten å holde kontakten på.

Reply via email to