[Radiant] 12,000 articles in a Radiant site?

[Loren Johnson]

Ok, so nobody said crazy...

That's good.

I guess there are three things that seem absolutely necessary to  
address then:

1. Entirely revisit Radiant's page caching -- possibly getting out of  
any proxy to ruby situation entirely to let Apache (or Nginx, or...)  
do their simple magic. Possibly simply using Radiant as a static site  
generator?

2. Depending on how the caching happens (static generation or not),  
implementing a core change to Page to store it's own full path and  
Page.find_by_url to remove the currently necessary recursion there.   
Sean -- why would we still need to keep it as a fall back?

3. New page admin interface

So, this doesn't sound like a rewrite of Radiant yet, hence maybe I  
get something worthwhile by using Radiant as the starting point.

Are there any changes to caching that we could consider for core  
which would also help make sense at this scale?

Are there any changes to the Admin page interface  ""?

L



On Sep 13, 2007, at 2:44 PM, Sean Cribbs wrote:

> Now, I imagine one of the largest slowdowns on your site is going  
> to be
> Page.find_by_url because it is recursive.  Radiant could really be  
> sped
> up by caching the URL in the database, which would reduce lookup time
> for most pages, and having the recursive method as a fallback.  If you
> want, we can hash over the design of this optimization together  
> (perhaps
> with John and Daniel) and apply it to the core.