> > Hi, I got this latest stuff and I'm not seeing any improvements in my > > case. I did some checking and it turns out that the cached stuff is > > working well, but it is the security that adds a ton of overhead when > > sorting is occurring. > > Read all your comments, but I have to take a closer look to fully > understand them. Will work on this tomorrow.
OK, I thought about this in the shower this morning (so you know it's quality thinking :)), and I think I might know what the problem is. In a nutshell, because providers downstream of the AuthorizationProvider can also deny access to a topic (imagine a file with the read-only bit flipped), the AuthorizationProvider has to query Next.HasPermission in order to answer the question "Does the current user have access to this file?" Absent caching, this means file I/O for every single operation, as the FileSystemStore actually attempts to open the file to figure out if the current user has permission. Well, caching *is* absent: I'm not caching the results of HasPermission (didn't think of it). That's pretty easy to fix, and if it works, I *think* it might provide a pretty serious perf boost. AuthorizationProvider.HasPermission gets called for almost every single operation, sometimes multiple times. In fact, given how much it gets called, I'm pretty surprised performance is even as good as it is. :) Adding this won't be too hard. I'll put it at the top of my list. Fingers crossed. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flexwiki-users mailing list Flexwiki-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flexwiki-users
