I have discovered that each worker process has its own copy of the cache and
it will be slightly different in each copy, until that process expires.
I believe the issue of blocking is with the lock in RecursionContext.
Disabling security does not eliminate this lock.
One of the biggest calculations is for a Topic.LastModified datetime. The
current algorithm is extremely inefficient in that it inspects all
topic*.awiki files, gets all the dates and sorts them into first created to
last modified order and then iterates through until the highest date. This
comes from using a generic routine needed for getting all revisions
datetimes and then reusing it for LastModified. Rather LastModified can
always be determined by inspecting topic.wiki for the creation date. I
suspect this change will bring a significant performance improvement for
numerous pages using wikitalk and for the LastModified.aspx page.
I can start on it Monday and will probably need 2 days to complete, but if
someone can get started before that it would be great.
John Davidson
On 11/22/07, John Davidson <[EMAIL PROTECTED]> wrote:
>
> Thanks. I have now tested with combinations of security/caching and all
> combinations still have a blocking behaviour.
>
> I believe this is because the application pool is set to a single worker
> process. When I increased this value to 4 on my single-proc server for my
> site, the blocking behaviour was eliminated. Limited testing has not yet
> shown any problems.
>
>
> Original technotes on Web Garden usage in IIS 6 advised against their use
> if SessionState was being managed InProc, but I do not think this would
> cause any headaches in the way FlexWiki operates. I thin I would like to set
> the maximum number of worker processes to 3 initially and see how that
> impacts real world throughput on flexwiki.com
>
>
> The change seems to require an actual reboot, as a restart of IIS did not
> improve response, but a reboot of my server did.
>
>
> John Davidson
>
> On 11/22/07, Craig Andera <[EMAIL PROTECTED] > wrote:
> >
> > > Initial testing was done on FlexWiki and my site with Security on, but
> > > I have confirmed same results on my site with security off, as well.
> > > This may indicate an issue with the cache code. Is there an easy way
> > > to disable the cache.
> >
> > Set the cache.disabled parameter in the namespace parameters to true.
> > That
> > just disables topic caching.
> >
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Flexwiki-users mailing list
> > Flexwiki-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/flexwiki-users
> >
>
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
