Sam,

I would opt for option 2, it’s the most flexible in the long run.

We have one client with 65.000 nodes (25 fields each) and they are using views + exposed filters to search them, but it’s an internal site so only a couple of users, the site is still quick (results are shown in less than a second). If you expect a lot of users searching, you might better look into apacheSolr to increase the speed.

Cheers

Peter

From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Sam Cohen
Sent: donderdag 8 maart 2012 15:51
To: development@drupal.org
Subject: [development] 115,000 records -- nodes or custom

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
Drupal Training & Services