On Sat, 5 Mar 2005, Bèr Kessels wrote:
Op zaterdag 5 maart 2005 03:02, schreef Gerhard Killesreiter:
What it really means is that there will be more nodes. On drupal.org the number of entries into the node table will about double. As long as nobody cares enough to provide hard test data to show Dries and us others that there is a negligible impact on performance this discussion is just hot air.
This is not an argument IMO.
Oh, it sure is. Performance is always a good argument.
A website should always scale.
In an ideal world.
And simply chopping things up might wiork for some cases, but is not an overall solution.
I am not convinced that comments as nodes makes too much sense anyway. The only thing I think that could be usefull for comments that they currently have not are file attachements.
Lets take an example: A site with thousands of articles and 10 of thousands of weblinks. If that starts to perform less good, the solution is not to pull weblinks out of the nodes system and create its own system, but the solution is to make overall node performance (AND maintanability!) better.
Well, there is only so much you can do from Drupal. If your database doesn't scale anymore, you need to reconsider things. You can of course always buy a faster computer, but this will not always be popular.
With the useability improvements the issue of maintainability of large amounts should be solvable.
I am not talking about maintainability.
Doing 50 node loads on a single page load can be fun. In contrast, the comments get pulled out in one single query.
if ever we go into comments as nodes, we must create some custom and improved queries indeed. I am thinking in lines of db_get_child_nodes($nid), which would return an array with all children nodes (comments) from a node.
If you want full nodes (nodeapi etc), this is not going to work. At least not without caching. If you don't want full nodes, we can just leave comments comments.
I will not take such a project on me, BTW :)
Maybe we should stop talking then. Cheers, Gerhard