A librarian here has created an index of student newspaper articles that go back to the 1900's. The 25,000+ records currently live happily in a MySQL table on our old site (not Drupal).
I was thinking of creating a new content type for the index and simply importing them with the node_import module. This approach worked well for me before when I imported about 2,400 records for something else... but 25,000 is a whole different ball game.
Would you implement a home-grown index with a new content type like this? Are there limits to the number of nodes Drupal can deal with? Would path_auto come to a screeching halt?
Test it
This appears to be one of those questions that is best answered by testing. 25k is not a lot of records or nodes, per se, but it is hard to predict potential pitfalls that one might encounter in a specific Drupal configuration. Since this is not so big that it wouldn't run on almost anything, why not copy your site onto a dev server - your laptop, perhaps - and give it a try. Even if it fails, it might give you some insight as to what workaround is required.
Cary Gordon
The Cherry Hill Company
Well, that's sensible
Well, that's sensible enough. Test it.
Regarding the notion that 25,000 nodes is not a lot of records... Sounds like I underestimate Drupal's ability to scale. Thanks, Cary.
25,000 records shouldn't be a problem
25,000 shouldn't be a problem for Drupal to handle. However - you may not want to import them all at the same time. Speaking from previous experience, depending on your php configuration settings, the node import script may time out.
Post new comment