-- How to increase Trends items.
In
src/configs/Config.php
there is a line:
nsconddefine('NUM_TRENDING', 50);
You can either directly edit this value or put in a LocalConfig.php file in the same folder:
<?php
nsdefine('NUM_TRENDING', some_bigger_value);
The job:
src/library/media_jobs/FeedUpdateJob.php
is responsible for downloading news feeds. It's been a while since I coded this, but I think the idea is that the constant MAX_FEEDS_ONE_GO (default 100) controls how many feeds are updated in an hour. If you have more feeds than that it cycles through them. So for example if you had 400 feeds, with the current setting it would take 4 hours to update all of them. The base unit for the MediateUpdater is an hour and I wanted to make sure all the jobs it runs would be done well within the hour on my hardware. The number 100 could easily be raise/experimented with. As of version 7, feeds are stored using the same kind of data structure as crawls, so should be capable of storing billions of feed items.
Best,
Chris
(
Edited: 2021-01-28)
In
src/configs/Config.php
there is a line:
nsconddefine('NUM_TRENDING', 50);
You can either directly edit this value or put in a LocalConfig.php file in the same folder:
<?php
nsdefine('NUM_TRENDING', some_bigger_value);
The job:
src/library/media_jobs/FeedUpdateJob.php
is responsible for downloading news feeds. It's been a while since I coded this, but I think the idea is that the constant MAX_FEEDS_ONE_GO (default 100) controls how many feeds are updated in an hour. If you have more feeds than that it cycles through them. So for example if you had 400 feeds, with the current setting it would take 4 hours to update all of them. The base unit for the MediateUpdater is an hour and I wanted to make sure all the jobs it runs would be done well within the hour on my hardware. The number 100 could easily be raise/experimented with. As of version 7, feeds are stored using the same kind of data structure as crawls, so should be capable of storing billions of feed items.
Best,
Chris