just a question
does unique items in follow tab applies to all account (whole account in TD) even if they're running in different stance?
unique items
- martin@rootjazz
- Site Admin
- Posts: 34696
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: unique items
applies to the accounts in THAT action only.
To not process duplicate items across multiple accounts, you have multiple options.
1) SHARED ACTIONS.
When you run a SHARED ACTION, the "already processed" lists for each account in the shared action is used to ensure, no item is processed if any of the accounts in the shared action have already processed the item. Additionally, the items that are processed in the shared action are recorded by all accounts and not processed by any account (in the shared action) in the future (even if an account is running a single account action)
2) Manual MERGE PROCESSED ITEMS.
On the action tabs (eg follow tab) you can select multiple accounts and select MERGE PROCESSED ITEMS. This will run a function to merge the processed items lists of all selected accounts at that point in time. Meaning no item processed by any account in the merge *already* will be processed again. This is a one-off merge, meaning the processed lists will diverge as you run more separate actions in future. Please note, if you perform this on the follow tab, only the followed processed items are merged.
3) Global processed logs - (most of the time people want this option)
Again, on the action tabs (eg follow tab) select your accounts, right click GLOBAL PROCESSED LOGS > ASSIGN (add)
What this does is sync all select accounts together their processed lists. This means the synced accounts will never process duplicate items regardless of what type of actions is used (shared / single). The difference between (2) "manual merge" is that this is a permanent sync, there will never be any duplication. Again this only applies to the action tab applied to (so only follow items if performed on the follow tab, only like items if performed on like tab)
viewtopic.php?f=15&t=11027
To not process duplicate items across multiple accounts, you have multiple options.
1) SHARED ACTIONS.
When you run a SHARED ACTION, the "already processed" lists for each account in the shared action is used to ensure, no item is processed if any of the accounts in the shared action have already processed the item. Additionally, the items that are processed in the shared action are recorded by all accounts and not processed by any account (in the shared action) in the future (even if an account is running a single account action)
2) Manual MERGE PROCESSED ITEMS.
On the action tabs (eg follow tab) you can select multiple accounts and select MERGE PROCESSED ITEMS. This will run a function to merge the processed items lists of all selected accounts at that point in time. Meaning no item processed by any account in the merge *already* will be processed again. This is a one-off merge, meaning the processed lists will diverge as you run more separate actions in future. Please note, if you perform this on the follow tab, only the followed processed items are merged.
3) Global processed logs - (most of the time people want this option)
Again, on the action tabs (eg follow tab) select your accounts, right click GLOBAL PROCESSED LOGS > ASSIGN (add)
What this does is sync all select accounts together their processed lists. This means the synced accounts will never process duplicate items regardless of what type of actions is used (shared / single). The difference between (2) "manual merge" is that this is a permanent sync, there will never be any duplication. Again this only applies to the action tab applied to (so only follow items if performed on the follow tab, only like items if performed on like tab)
viewtopic.php?f=15&t=11027
- martin@rootjazz
- Site Admin
- Posts: 34696
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: unique items
just a quick question. does merging logs increase the usage of CPU/RAM?
I noticed that my CPU usage is up to 90% and my RAM is up to 2,800MB + at some time ( is that number normal for 350 accounts with 27 threads) (home machine with i7 4.20Ghz CPU and 30GB RAM)
- martin@rootjazz
- Site Admin
- Posts: 34696
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: unique items
yes it will use CPU + RAM, as the files are read (CPU) into memory (ram) then copied / merged to other DB records (CPU)lavalamp wrote: ↑Thu Dec 15, 2022 6:19 pmjust a quick question. does merging logs increase the usage of CPU/RAM?
I noticed that my CPU usage is up to 90% and my RAM is up to 2,800MB + at some time ( is that number normal for 350 accounts with 27 threads) (home machine with i7 4.20Ghz CPU and 30GB RAM)
Should go back down though. It tries to do this as quickly as possible, so that means using all CPU resources the OS allows