> What are 'vendor' folders at all?
vendor: Composer (php librarry manager) dumps libraries into vendor folder in the same directory where `composer update` is called. This is default behavior of composer. One way to think of the vendor directory is as a more generic form of "lib"
>how did you measure the impact of these
>modifications? Did you reindex from scratch after every modification?
First time I ran tracker never stopped indexing. I monitored tracker-miner-fs.log and also with (/usr/libexec/tracker-extract -v 2). At some point you would expect logging to stop when it becomes idle. But it didn't. Only after tweaking and hard resetting situation improved dramatically. I found similar bugs on bugzilla, I will comment there.
>I have the feeling here and other places above that you are
>extrapolating personal usecases to entire user bases.
Perhaps yes. But my intention is to put indexing at minimal level. In previous version of tracker I used with Ubuntu Gnome, meta.db in ~/.cache used to grow over 1 GB. Again I found the relative bug and will continue discussion over there. Let's not pollute this bug discussing tracker issues.
[Sorry for late reply, I didn't get any notification]
>Because nobody provided patches. I will welcome yours at /bugzilla. gnome.org/ enter_bug. cgi?product= tracker
>https:/
> What are 'vendor' folders at all?
vendor: Composer (php librarry manager) dumps libraries into vendor folder in the same directory where `composer update` is called. This is default behavior of composer. One way to think of the vendor directory is as a more generic form of "lib"
I filed a bug https:/ /bugzilla. gnome.org/ show_bug. cgi?id= 782562
>how did you measure the impact of these
>modifications? Did you reindex from scratch after every modification?
First time I ran tracker never stopped indexing. I monitored tracker- miner-fs. log and also with (/usr/libexec/ tracker- extract -v 2). At some point you would expect logging to stop when it becomes idle. But it didn't. Only after tweaking and hard resetting situation improved dramatically. I found similar bugs on bugzilla, I will comment there.
>I have the feeling here and other places above that you are
>extrapolating personal usecases to entire user bases.
Perhaps yes. But my intention is to put indexing at minimal level. In previous version of tracker I used with Ubuntu Gnome, meta.db in ~/.cache used to grow over 1 GB. Again I found the relative bug and will continue discussion over there. Let's not pollute this bug discussing tracker issues.