For some reason I did not see any emails from you for a full 10 days after
you sent them. I wonder why this was? Perhaps Apache infrastructure was
misbehaving but I apologize for the late response.
On Sun, May 21, 2023 at 8:59 AM Karl Wright wrote:
> Hi - the big source of bloat for hopcount
Hi - the big source of bloat for hopcount processing is the delete
dependencies table, and the options provided allow you to not track those
at all. The other tables (intrinsiclink and hopcount) are 1:1 with the
documents themselves, so these were not considered worth optimizing.
It may be
Hi Karl,
I am terribly sorry for bothering you while you are busy.
For this issue, I've tried to add a property for disabling hopcount
logging to the database only for jobs with its hopcount mode set to
"keep unreachable documents, forever" in the "Hop Filters" tab.
I would appreciate it if you
Hi Karl,
Thank you for taking time out of your busy schedule to reply.
> There is an option on the "hopcount" tab of your job to disable hopcount
You mean setting "Hop count mode" to "keep unreachable documents,
forever" in the "Hop Filters" tab?
Yes, I did it, however, it seems that the
There is an option on the "hopcount" tab of your job to disable hopcount
tracking entirely.
Karl
On Tue, May 9, 2023 at 11:49 PM Mingchun Zhao
wrote:
> Hi Karl,
>
> Could you please advise me on tracking hopcount.
> I'm using ManifoldCF 2.24 with PostgreSQL 12.14 as the database for now.
> In
Hi Karl,
Could you please advise me on tracking hopcount.
I'm using ManifoldCF 2.24 with PostgreSQL 12.14 as the database for now.
In my case, I don't need to use the 'Hop Filters' feature so I'd like
to disable tracking hopcount and reduce the insert/update/delete load
on the 'intrinsiclink' and
