Normal
I don't know the answer to this. As you can derive from RoChess's post, he is taking about a table called [node] and [node__node]. It would seem to me that the plugin actually go and create a "node" for each actor for example. Now this should be a one time thing then, because the only time this will need to be done again, is when info is updated or new movies are added. But from what I found, indexing the actual value field where this nodes is being build from, causes an increase in speed. This gives me the idea that the nodes are repeatedly build every time you access the plugin "category" page. Because each movie has a field that list all the actors, it would mean that the plugin has to scan and work through each cell. So I don't think any indexing will help with this. I might be wrong, and if we actually investigate the code, we will be able to not speculate and give an exact answer. And I don't think anyone is up for that yet.
I don't know the answer to this. As you can derive from RoChess's post, he is taking about a table called [node] and [node__node]. It would seem to me that the plugin actually go and create a "node" for each actor for example. Now this should be a one time thing then, because the only time this will need to be done again, is when info is updated or new movies are added.
But from what I found, indexing the actual value field where this nodes is being build from, causes an increase in speed. This gives me the idea that the nodes are repeatedly build every time you access the plugin "category" page. Because each movie has a field that list all the actors, it would mean that the plugin has to scan and work through each cell. So I don't think any indexing will help with this.
I might be wrong, and if we actually investigate the code, we will be able to not speculate and give an exact answer. And I don't think anyone is up for that yet.