[development] 115,000 records -- nodes or custom

[Michael Prasuhn]

FWIW, Drupal.org does not make heavy use of CCK (change nodes, and a few
other types are some of the first content types built mostly on CCK).
Projects and especially the issue queue make use of custom tables, and
highly tuned views, using multiple instances of denormalization for
performance.

Ms. Nancy Wichmann wrote:
> Let's see, Drupal.org has more than 10 times the nodes plus many more
> comments. It runs D6 and uses Views. And it is usually fast enough.
>  
> /*Nancy*/
>  
> Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L.
> King, Jr.
> 
>     ------------------------------------------------------------------------
>     *From:* Sam Cohen
> 
>     The client currently has a searchable database of a 115,000 records
>     written in cold fusion in a separate database on a separate server. 
> 
>     They would like me to bring it into their Drupal 6 site or at least
>     onto the same server.
> 
>     I can do this in two ways:
>     1.   As a custom module running off it's own db.
>     2.  Or I can make it a content type and use Views for the interface. 
> 
>     My preference is to just use CCK/Views for maximum flexibility --
>     but I question whether or not it's wise to add a 115k records to the
>     node and other tables and what type of impact this might have on
>     overall site performance.  (Any other downsides?)
> 
>     Anyone have any advice/suggestions?  If it was your project would
>     you code it separately or use CCK/Views.
> 

-- 
__________________
Michael Prasuhn
503.512.0822 office
mike at mikeyp.net