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

Janez Urevc janez at janezek.org
Thu Mar 8 17:56:01 UTC 2012

2nd option definitely. Just do it with caution, test for performance early
enough, check for slow queries, etc

Drupal can scale, you just have to think and understand what are you doing.

Why not D7?

Dne 8. mar. 2012 15:57 je "Sam Cohen" <sam at samcohen.com> napisal/-a:

> Hi.
> I was hoping for some advice.  I recently took over an existing Drupal
> site for a nonprofit.
> 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.
> Thanks,
> Sam
> Sam Cohen, Principal
> New Media Solutions <http://new-media-solutions.com>
> Drupal Training & Services
> <http://twitter.com/samcohen>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20120308/b7e8f10b/attachment-0001.html 

More information about the development mailing list