Hmm.
Does this configuration change mean that Windows-based authentication scenarios
will continue to be slow/have the CPU spiking problem?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Davidson
Sent: Monday, November 26, 2007 2:58 PM
To: FlexWiki Users Mailing List
Subject: Re: [Flexwiki-users] www.flexwiki.com cutover Thursday
I can confirm the change in performance is _orders_ of magnitude faster. This
is now at least as fast as FlexWiki 1.8 appeared to be. Perhaps David could
make similar configuration changes and try rerunning the timing tests?
I find it curious that disabling security did not have the same effect, except
I guess that the disabling function just ignores a permission check rather than
fully removing it from the pipeline. Would it be possible to have security
disabled remove the AuthorizationProvider from the pipeline?
The inclusion of new BuiltInTopics should only require definition in
BuiltInTopicsProvider and some minor changes to the NamespaceManager to include
the additional references. There are advantages and disadvantages to including
this and similar functionality in BuiltInTopics. The advantages are that these
topics would now be skinned the same as the rest of the wiki and that they
would be easy to revise to provide additional functionality.
Of course now that the topic has been created it just becomes one more tool and
doesn't need to be a BuiltInTopic to be of use.
The good news is that this version truly is a valid Release Candidate just as
you thought.
John Davidson
On 11/26/07, Craig Andera <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
So, I went into the www.flexwiki.com<http://www.flexwiki.com> configuration and
changed
role:BUILTIN\Administrators to "authenticated". That seems to have solved
the problem with lsass spiking the CPU, and better seems to have solved the
performance issues with the site. I can now open up several tabs, point each
of them to the LastModified page, and none time out.
Which is good, because I was a bit leery of putting the last modified page
in as WikiTalk in the built-in provider: it would complicate the pipeline
model.
The bad news is I have no idea why WindowsIdentity.IsInRole (which is the
only thing that could be causing the CPU usage) is causing such a slowdown.
Maybe it's just inherently slow because it needs to go talk to the LSA so
much.
> -----Original Message-----
> From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> [mailto:flexwiki-<mailto:flexwiki->
> [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>] On Behalf Of John Davidson
> Sent: Monday, November 26, 2007 11:33 AM
> To: FlexWiki Users Mailing List
> Subject: Re: [Flexwiki-users] www.flexwiki.com<http://www.flexwiki.com>
> cutover Thursday
>
> I have modified the topic RecentlyModified [1], so that it now has
> selectable number of last modified topics and selectable namespace,
> with default of 100 topics and the current namesapce. It is proposed
> to add this as a new BuiltInTopic to replace LastModified.aspx . This
> solution appears more responsive and flexible than the current
> implementation.
>
> I have not included the Author filter capability, though a separate
> topic could be created to provide this functionality. This feature is
> in part responsible for the poor performance of LastModified.aspx.
>
> Additionally if this is converted to become a BuitlInTopic then the
> LockTopic.aspx page output would also be converted (though
> LockTopic.aspx would remain as there is actual functionality, even
> when page is not displayed).
>
>
> [1] http://www.flexwiki.com/default.aspx/FlexWiki/RecentlyModified.html
>
> John Davidson
>
> On Nov 23, 2007 9:20 PM, Craig Andera <[EMAIL PROTECTED]<mailto:[EMAIL
> PROTECTED]>> wrote:
> > > I will also look at LastModified.aspx to see why it fails when
> > > wikitalk does not ;)
> >
> > The one difference I can think of is that there's no RequestContext
> active
> > in LastModified.aspx. RequestContext is used to do some per-request
> caching
> > in the AuthorizationProvider.
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> ----
> > 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<mailto: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<mailto: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<mailto: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
