[Neos] How to handle large numbers of records/nodes
aske at moc.net
Wed Jul 9 15:45:18 CEST 2014
With this change from Rens you can https://review.typo3.org/#/c/30481/
Will be available in 1.2
There has already been quite some discussions on how to make the tree handle large numbers of nodes on the same level, so there’s plenty of steps to take to improve the situation. Mainly it’s lacking development resources, so could be something your project could help improve in Neos? That’s how most Neos development is driven currently.
On 09 Jul 2014, at 12:49, Søren Malling <soren.malling at gmail.com> wrote:
> Hi Sebastian,
> The 9000 records can be categorized in three different types, so imagine
> three pages having these 9000 records as childnodes.
> Can i somehow exclude a specific nodetype from the tree, even though it
> uses TYPO3.Neos:Page as superType?
> Then i could imagine a simple module displaying the specific nodetype in a
> list and simply link to the url and gives the frontend editing.
> On Wed, Jul 9, 2014 at 10:09 AM, Sebastian Kurfürst <sebastian at typo3.org>
>> Hey Søren,
>> I think it depends very much if all these 9000 records are on one level
>> in the tree (which would be more difficult for now), or if the records
>> are structured intrinsically in a different way.
>> I think for searching etc, ElasticSearch and TYPO3CR Search are good
>> candidates to handle that.
>> Neos mailing list
>> Neos at lists.typo3.org
> Neos mailing list
> Neos at lists.typo3.org
More information about the Neos