By edalcin on
Dear Drupalers,
I'm curious about the capacity of Drupal in handling big catalogs as nodes. Therefore, I would like to know how big your nodes are. I mean, for example, considering each node record as a book, such as in bibliography module, how many books can I have handled bu Drupal, with a reasonable performance? Can I have a library of 500.000, or even 1.000.000 books handled by Drupal? How big are your Drupal nodes?
Thanks in advance!
Best
Comments
_
Look at the URL of this page - your post is the 765,648th node...
-
I've heard there are some folks around here with some pretty big nodes.
Seriously though, straight text is great, but when you start adding images, CCK fields, and other assorted material to a node, it will affect performance.
Yes it will, but Drupal is
Yes it will, but Drupal is very capable of handling thousands and thousands of very heavily customized node types (by means of CCK, views, panels.. you know the drill) and there's not much the Boost module, AuthCache and core performance options can't handle...
I've heard there are some
And that's exactly what I'm talking about. How reasonable is to propose Drupal as a "big collections catalog system" (with a bunch of CCK Fields) ?
.
Well, there are a lot of variables to consider. If you are on a shared server, you will be at a distinct disadvantage in terms of performance, as opposed to being on a VPS, for example. The number of visitors on a site at a given time is another factor affecting performance.
May I recommend the following, which provides enough information on performance to last at least a few days:
http://2bits.com/articles/drupal-performance-tuning-and-optimization-for...